The rule is "newline or semicolon", so whitespace does carry a meaning.
IMHO this is a mistake, because it is often fragile and can lead to code that the compiler reads differently than the human sitting in front of the screen.
And yes, I maintain that that's a mistake in javascript and Go too.
Apart from that, I agree with your conclusions. I'll try it out as soon as they release the compiler.
JavaScript automatic semicolon insertion is definitely considered to be a mistake (judging by es-discuss), but many many other languages allow newlines as statement separators without problems. It seems to be fine as long newlines are only allowed under certain circumstances within expressions, such as only in grouping constructs () [].
Not quite consistently, semicolons are optional: http://confluence.jetbrains.net/display/Kotlin/Grammar#Gramm...
The rule is "newline or semicolon", so whitespace does carry a meaning.
IMHO this is a mistake, because it is often fragile and can lead to code that the compiler reads differently than the human sitting in front of the screen.
And yes, I maintain that that's a mistake in javascript and Go too.
Apart from that, I agree with your conclusions. I'll try it out as soon as they release the compiler.