Golang syntax for declearning struct literal with unexported fields

Question

I've got a largish struct which until just now I was instantiating with the struct literal syntax, e.g.:
Thing{
  "the name",
  ...
}

I've just added an unexported field the Thing struct and now Go is complaining: implicit assignment of unexported field 'config' in Thing literal.

Is there any way I can continue using the literal syntax even though there's now an unexported field on the struct?

Gopher · Accepted Answer

You can only use composite literals to create values of struct types defined in another package if you use keyed values in the literal, because then you are not required to provide initial values for all fields, and so you can leave out unexported fields (which only the declaring package can set / change). If the type is declared in the same package, you can set unexported fields too: t := Thing{ Name: "the name", someUnexported: 23, } But you can only provide initial values for exported fields if the type is declared in another package, which is not a surprise I guess: t := otherpackage.Thing{ Name: "the name", // someUnexported will implicitly be its zero value } If you need values of the struct where the unexported fields have values other than the zero value of their types, the package itself must export some kind of constructor or initializer (or setter method), because from the outside (of the package), you can't change / set unexported fields.

Go Language

Similar Questions

Embedding Structs in Go with pointer or with value, what is difference between them?

How to Type converting slices of interfaces in Go?

How to efficiently concatenate strings in Go?

On a mission to build Next-Gen Community Platform for Developers

Facebook

Twitter

Linkedin

Instagram