Kevin Smith wrote:
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?
That old chestnut! (Unquote "a" for better ambiguity.)
http://esdiscuss.org/topic/let-and-strict-mode
I honestly forget how we decided to go for let at start of statement
followed by [ -- but I do recall we agreed not to have
name-binding-sensitive parsing(!). I.e., we would not look for 'var let
= ...' and treat 'let' in that (hoisted) scope as a non-keyword.
/be
_______________________________________________
es-discuss mailing list
[email protected]
https://mail.mozilla.org/listinfo/es-discuss
