If you haven't found any "serious response", maybe it's because you haven't searched enough. Here is a "clear, detailed, not demeaning, and constructive" answe

If you haven't found any "serious response", maybe it's because you haven't searched enough. Here is a "clear, detailed, not demeaning, and constructive" answer of Ian Lance Taylor that addresses your concerns: https://groups.google.com/d/msg/golang-nuts/smT_0BhHfBs/MWwGlB-n40kJ https://groups.google.com/d/msg/golang-nuts/smT_0BhHfBs/MWwG... I would guess his answer will not suit you, but you can hardly argue the Go team ignores the issue or refuses to talk about it.