Why is JavaScript designed to automatically insert a semicolon after a return, followed by a new line?

Question

I just ran into a problem where I did this:

return
    isSomething() &&
    isSomethingElse();

which does not work because javascript inserts a semicolon after returning, making the above equivalent:

return;
isSomething() && isSomethingElse();

This completely puzzled me about why he was doing this. I found some StackOverflow questions on the topic (like this , this and this ), but they just explain when this is done, referring to the specifications .

, return;, javascript ( goto , , - javascript, ). , .

, . ?

: , . , , , , JavaScript, , . , , , , , .

Answer 1

, , , . , :

• - - , .
• - , return , .
• return, , , .

Answer 2

Javascript "" , , , , . , . :

The semicolon is only obligatory when you have two or more statements on the same line:

var i = 0; i++        // <-- semicolon obligatory
                      //     (but optional before newline)
var i = 0             // <-- semicolon optional
    i++               // <-- semicolon optional

, , , Javascript , , , .

Answer 3

"", .

Javascript .