One year of Go

[Walter Bright]

Nick Sabalausky wrote:
> Semicolons are normally a bikeshed issue, but if optional-semicolons are 
> done in a way that means accidentally putting '{' on the wrong line results 
> in silently modified behavior, then that's not a bikeshed, that's just a 
> broken language design.

I agree that the sometimes lines are significant and sometimes not is, in the 
end, more confusing than enlightening.

Especially when, as in Andrei's example, *very* common forms compile without 
error and produce unexpected results.