On Aug 31, 2015, at 7:11 PM, Brendan Eich wrote:
> We are in rapid-release hell/heaven.
>
> This means errata can be issued, and engines can implement the better
> resolution for those errata, compared to what the last major-version _de
> jure_ spec mandated.
>
> Why not?
>
> /be
The possib
>
> I don't see how strict/sloppy mode effects the behavior of top-level
> lexical declarations. Does the behavior depend on strict mode?
>
No, V8 just currently disallows the use of let/const/class outside of
strict mode.
___
es-discuss mailing list
es-
>
> We should have just made toplevel let/const/class create global
> properties, like var. This is how it was proposed originally
Can you provide (or link to) a more specific proposal?
Kevin
___
es-discuss mailing list
es-discuss@mozilla.org
https://m
I don't see how strict/sloppy mode effects the behavior of top-level lexical
declarations. Does the behavior depend on strict mode?
I agree with Brendan: I vote for changing this if we can.
Saam
> On Aug 31, 2015, at 7:11 PM, Brendan Eich wrote:
>
> We are in rapid-release hell/heaven.
>
We are in rapid-release hell/heaven.
This means errata can be issued, and engines can implement the better
resolution for those errata, compared to what the last major-version _de
jure_ spec mandated.
Why not?
/be
Adam Klein wrote:
Note that this behavior in v8/Chrome is only about sloppy m
Note that this behavior in v8/Chrome is only about sloppy mode. In strict
mode, v8 implements the ES6 spec (and we'll likely have support for lexical
declarations in sloppy mode soon).
Though I personally agree that the top-level lexical scoping in ES6 seems
unfortunate.
On Mon, Aug 31, 2015 at 9
I think a better solution would have been to have all top-level
let/const/class
variables just be local to that specific Program. That's how I originally
implemented it in JavaScriptCore, and now I'm going back and "fixing"
it to be as it is defined in the Spec.
(That said, I agree that allowing th
Personally I am a fan of Chrome's CURRENT solution:
```
Uncaught SyntaxError: Block-scoped declarations (let, const, function,
class) not yet supported outside strict mode
```
- Matthew Robb
On Mon, Aug 31, 2015 at 12:08 PM, Jason Orendorff wrote:
> Hi everyone. Can we talk about the global le
Hi everyone. Can we talk about the global lexical tier?
This was a mistake, a real blunder. We all should have known better.
An extensible intermediate scope implies dynamic scoping. The referent
of an identifier can change only once, but it can change. It's like an
implicit `with` block around *a
9 matches
Mail list logo
