title: Golang struct literal syntax with unexported fields
body: <p>I've got a largish struct which until just now I was instantiating with the struct literal syntax, e.g.:</p>
  
  <pre><code>Thing{
    "the name",
    ...
  }
  </code></pre>
  
  <p>I've just added an unexported field the <code>Thing</code> struct and now Go is complaining: <code>implicit assignment of unexported field 'config' in Thing literal</code>.</p>
  
  <p>Is there any way I can continue using the literal syntax even though there's now an unexported field on the struct?</p>