>
>
> But IIRC (and from reading http://people.mozilla.org/~
> jorendorff/es6-draft.html, looking for LetOrConst uses), ES6 supports let
> in all contexts, reserved word or not.
>
Yes, I see that now. Has anyone done compatibility-hazard analysis for
this breaking change?
;
let["a"].foo() // Fine in ES5 non-strict, fails in ES6?
> Did we really do any good trying to reserve yield *or* let in ES5? I don't
> see it, now.
>
>
It looks like the combination of context-sensitive lexing and the placement
of the "use strict" prologue interacts...poorly. (Cue Indiana Jones and
the Last Crusade.)
I see now that Allen has moved strict reserved words out of the lexical
grammar. Cool!
_______________________________________________
es-discuss mailing list
[email protected]
https://mail.mozilla.org/listinfo/es-discuss
