How to clone a structure with unexported field?

by

You can’t. That’s the point of unexported fields: only the declaring package can modify them.

Note that if the T type is declared in another package, you can’t even write:

p := somepackage.T{"some string", []int{10, 20}}

because this would implicitly try to set the unexported T.is field and thus results in a compile-time error:

implicit assignment of unexported field 'is' in somepackage.T literal

If you own (or you can modify) the package, best is to provide a Clone() method or function, or provide a SetIs() method for the type T. If a 3rd party package does not provide such functionality, there’s nothing you can do about it.

Note that using package unsafe it is possible to do such things, but as its name says: it’s unsafe and you should stay away from it.

Also note that you can create new values of T where is is not copied but will be the zero value of its type (which in case of []int will be nil):

var r somepackage.T
s := somepackage.T{S: p.S}

fmt.Printf("%q\n", r)
fmt.Printf("%q\n", s)

Which will output:

{"" []}
{"some string" []}

But you can’t set any non-zero value for the unexported field T.is.

Do note that you can make “exact” copies of structs having unexported fields by simply assigning them to another struct variable (of the same type), which will properly copy the unexported fields too.

Like in this example:

type person struct {
    Name string
    age  *int
}

age := 22
p := &person{"Bob", &age}
fmt.Println(p)

p2 := new(person)
*p2 = *p
fmt.Println(p2)

Which will output (try it on the Go Playground):

&{Bob 0x414020}
&{Bob 0x414020}

Which we can even generalize using reflect without relying on the concrete type:

type person struct {
    Name string
    age  *int
}

age := 22
p := &person{"Bob", &age}
fmt.Println(p)

v := reflect.ValueOf(p).Elem()
vp2 := reflect.New(v.Type())
vp2.Elem().Set(v)
fmt.Println(vp2)

Try this one on the Go Playground.

But what we can’t do is change the person.age unexported field to point to something else. Without help of the declaring package, it can only be nil or the same pointer value (pointing to the object as the original field).

More Related Contents:

  1. What is the correct way to retrieve length of an array added a field in nested struct in golang
  2. What are the use(s) for tags in Go?
  3. What are the use(s) for struct tags in Go?
  4. Generic Structs with Go
  5. How to access unexported struct fields
  6. package’s type cannot be used as the vendored package’s type
  7. How to set default values in Go structs
  8. Why are interfaces needed in Golang?
  9. Golang embedded struct type
  10. Struct in for loop initializer
  11. When do you embed mutex in struct in Go?
  12. Go struct tags with underscore before function names
  13. Why can’t I append to a slice that’s the property of a struct in golang?
  14. Why do 2 time structs with the same date and time return false when compared with ==?
  15. What is the possible use case for defer?
  16. golang get only one stat from json
  17. cancel a blocking operation in Go
  18. Organizing a multiple-file Go project [closed]
  19. Can I create shared test utilities?
  20. How do you create a new instance of a struct from its type at run time in Go?
  21. Order of the code and performance
  22. How to get the directory of the currently running file?
  23. Instance new Type (Golang)
  24. What is the idiomatic way in Go to create a complex hierarchy of structs?
  25. Is this casting in golang?
  26. Go-compiled binary won’t run in an alpine docker container on Ubuntu host
  27. Return pointer to local struct
  28. go build can’t find a revision
  29. Passing an arbitrary function as a parameter in Go
  30. Convert an integer to a byte array

Leave a Comment