Discuss
  • Message History
John Lenz (2014-01-24T17:27:00.000Z)
On Fri, Jan 24, 2014 at 9:17 AM, Oliver Hunt <oliver at apple.com> wrote:

> I believe the conclusion with |let| was to identify let syntax:
> let foo(=*) is syntactically unambiguous, just a bit more work to identify.
>
> yield is only valid in generators (function*) so that gets reserved the
> moment you enter a generator definition
>

That is great, that only leave block scoped function declarations (and
anything else I'm not aware of)


>
> —Oliver
>
> On Jan 24, 2014, at 9:11 AM, John Lenz <concavelenz at gmail.com> wrote:
>
> You don't get "let", "function" block scoping, "yield" or other
> incompatible constructs. (let and yield aren't a reserved word in ES5
> "loose)
>
>
> On Fri, Jan 24, 2014 at 8:49 AM, Tab Atkins Jr. <jackalmage at gmail.com>wrote:
>
>> On Fri, Jan 24, 2014 at 8:48 AM, John Lenz <concavelenz at gmail.com> wrote:
>> > For static language parsers there seems to be a bit of a dilemma with
>> ES6
>> > modules.  I would appreciate a correct or hint.
>> >
>> > Here is my understanding:
>> >
>> >   - standard scripts as we know them today will parse in the browser as
>> > "loose" code
>> >   - scripts with the standard "use strict" will parse as "strict" with
>> > access to all ES6 goodness
>>
>> Loose code will also get all the ES6 goodness.  1JS and all that.
>>
>> ~TJ
>>
>
> _______________________________________________
> es-discuss mailing list
> es-discuss at mozilla.org
> https://mail.mozilla.org/listinfo/es-discuss
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/es-discuss/attachments/20140124/0b768b51/attachment.html>
domenic at domenicdenicola.com (2014-01-31T21:14:18.807Z)
On Fri, Jan 24, 2014 at 9:17 AM, Oliver Hunt <oliver at apple.com> wrote:

> I believe the conclusion with `let` was to identify let syntax:
> `let foo(=*)` is syntactically unambiguous, just a bit more work to identify.
>
> `yield` is only valid in generators (`function*`) so that gets reserved the
> moment you enter a generator definition
>

That is great, that only leave block scoped function declarations (and
anything else I'm not aware of)
Edit