News for hackers. Stuff that matters.
Re:Backwards compatibility in Go (2015) by twotwotwo on Wednesday January 11, 2017 @07:40PM (#13378891)
Using the unkeyed initializer syntax is discouraged anyhow: https://golang.org/cmd/vet/#hdr-Unkeyed_composite_literals

Unkeyed syntax also doesn't work for a struct in another package with at least one private field.

One common exception is a vector type that isn't expected to change--RGBA, XYZ, LatLon, etc.

Re:Backwards compatibility in Go (2015) by Merovius on Thursday January 12, 2017 @03:24AM (#13380718)
The issue is that even if you only consider keyed initializers, adding fields is a breaking change, strictly speaking. I tried making clear that I use the compatibility guarantee as a basis in the introduction and I mention this exception more thoroughly in the section about adding fields.