"some changes break with ES5.strict" is confusing -- do you mean 'let' works instead of being a future reserved word, whereas in (3, below) 'let' is not reserved at all?
Agreed.
Dave proposed *not* removing the global object, but keeping the free variable error analysis. Most of the win is in the latter, for users. Indeed removing the global object is harder for implementors who've already sunk the cost, and lots of JS that might want to migrate into module {...} to get early typo errors depends on window.foo aliasing var foo (object detection at top level). If you mean other breaking runtime changes, please note that early on a bunch of us threw in the towel on typeof null == "null". We're still hopeful for completion reform, but Dave's proposal ups the ante: runtime semantic shifts are bad for users and implementors, worse than before with whole-script opt-in.
I think counting modes has to count to three, as you enumerated above (if I understand your (1) correctly). /be |
_______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
