I’m quite far from the ongoing Go community discussions, but this seems to be a perfect example?<p>> We’ve discusses this internally and decided...<p>As one commenter on the PR points out, they’ve discussed it internally, now it’s time to discuss as a community, but this issue has still been closed.<p>I don’t have an opinion on the actual topic here, but if Google don’t want to be perceived as doing whatever they like with Go and not involving the community, then they have to at least have these discussions. Even if they come to the table with strong opinions and good reasons, keeping up the appearance of community involvement like in this issue creates a culture of Go being community driven, and right now that culture is lacking.