You're right that your (very contrived) examples are different. But if anybody on my team writes code like this, it doesn't pass code review.
console.log("woof")
(function() { console.log("foo") })()
console.log("woof")
void function() { console.log("foo") }()
On this topic, it could so easily have been different; I found this interesting from Brendan Eich [1]:
> I wish I had made newlines more significant in JS back in those ten days in May, 1995. Then instead of ASI, we would be cursing the need to use infix operators at the ends of continued lines, or perhaps or brute-force parentheses, to force continuation onto a successive line. But that ship sailed almost 17 years ago.
> ...My two cents: be careful not to use ASI as if it gave JS significant newlines...
[0] this is technically a lie because everybody needs learn the other one whether they use semicolons or not: don't put a linebreak after the "return" keyword :) [1] https://brendaneich.com/2012/04/the-infernal-semicolon/
Here's an even easier and clearer one: finish every statement with a semicolon.
function hello() {
var x = 0;
return
{
x: x,
y: y
};
};