2011/4/18 Bob Nystrom <[email protected]>:
> The semicolon elision rules from what I've seen are a good bit simpler than
> the current insertion ones: If a token that can't end an expression or
> statement precedes a newline, eat the newline.
If I understand semicolon elision, then
myLabel:
for (;;) {}
would be interpreted as
myLabel: ;
for (;;) {}
That case should fail fast in all cases with undefined labels, as long
as eval can't be used to break/continue to labels not defined in the
evaled code, and could be addressed with a rule similar to insertions
rule against fabricating no-ops.
But it definitely does change behavior around mixed unary/binary
operators in ways that affect current coding practices:
var x = "foo"
+ "bar"
though lint tools' unused value warnings should catch this particular example.
_______________________________________________
es-discuss mailing list
[email protected]
https://mail.mozilla.org/listinfo/es-discuss
