News for hackers. Stuff that matters.
Re:First chapter of Kernighan and Donovan's new Go book [pdf] by edsrzf on Monday October 19, 2015 @06:14PM (#10416172)
One non-obvious downside is that the Go 1 compatibility guarantee doesn't apply to struct literals that don't use field names. (I suspect you're aware of this, but other readers might not be.)

So it's possible that a future version of Go could add a field to some struct you're using and your code will stop compiling when you upgrade. It's an easy fix, of course, so it's not that big of a deal, but it's worth realizing.

Re:First chapter of Kernighan and Donovan's new Go book [pdf] by jerf on Monday October 19, 2015 @06:21PM (#10416202)
The point is that if I'm using stuct literals, I want the compiler to stop me for those structs.

I'm explicitly rejecting the idea that all struct changes should be possible without producing compiler errors. Compilers errors when the guarantees your code is based on changes is a feature, not a bug.