On 2 Oct 2013, at 10:45, Petka Antonov petka_anto...@hotmail.com wrote:
In current version, this works just fine:
var let = 6;
Note that `let` was reserved in strict mode (only) in ES5, meaning that even as
per ES5 that snippet only works in sloppy mode.
On Oct 14, 2013, at 9:49 AM, Mathias Bynens wrote:
On 2 Oct 2013, at 10:45, Petka Antonov petka_anto...@hotmail.com wrote:
In current version, this works just fine:
var let = 6;
Note that `let` was reserved in strict mode (only) in ES5, meaning that even
as per ES5 that snippet
In current version, this works just fine:
var let = 6;
That could work with let being a contextual keyword.
But how about:
var a = 5;
let(a = 6)
{
alert(a)
}
Currently that does:
var a = 5;
a = 6;
let(6);
//purposeless block
{
Never mind, I just realized the let on MDN page is completely different
from ES6 let.
___
es-discuss mailing list
es-discuss@mozilla.org
https://mail.mozilla.org/listinfo/es-discuss
It would be easier if we had the other let-specific special forms,
wouldn't it?
ES6 draft makes let a reserved identifier. This is not backward
compatible, but we're trying to find out what we can get away with. The
fallback if we can't reserve is to do what we will do with 'yield (not
yet
5 matches
Mail list logo
