One year of Go

[Sean Kelly]

Russel Winder Wrote:
> 
> So all in all whether it is a serious issue or not, it doesn't actually
> matter than much when writing Go code.

What got me was "if you don't, there are situations that ... may give the wrong result."  I'm fine with eliminating semicolons, but why is this syntax allowed if it silently produces surprising results?  It seems like a trivial change to require the proper syntax, and not doing so makes me wonder if there are other such flaws as well.