One year of Go

[jfd]

== Quote from Sean Kelly (sean at invisibleduck.org)'s article
>> In Go code, the only place you typically see semicolons is
>> separating the clauses of for loops and the like; they are not
>> necessary after every statement

> To me, what they're saying is that their syntax is broken and so it
> forces a convention upon the users to deal with the issue.

Also, doesn't semicolon also help recover from bad syntax, by skipping to next
semicolon, or it not necessary any more?