Re: Reflect.toStringSpec proposal

This was also pointed out to me elsewhere: ```js const ToStringSpec = x => `${x}`; ``` On Tue, Dec 13, 2016 at 9:05 PM, Jordan Harband wrote: > Here you go: `require('es-abstract').ToString` https://www.npmjs. > com/package/es-abstract > > On Tue, Dec 13, 2016 at 7:44 PM,

Re: Reflect.toStringSpec proposal

Here you go: `require('es-abstract').ToString` https://www.npmjs.com/package/es-abstract On Tue, Dec 13, 2016 at 7:44 PM, Bergi wrote: > Sergey R schrieb: > >> I want to propose a new language feature — Reflect.toStringSpec. >> > > `Reflect.toString` or `Reflect.toStringSpec`?

Re: Reflect.toStringSpec proposal

Sergey R schrieb: I want to propose a new language feature — Reflect.toStringSpec. `Reflect.toString` or `Reflect.toStringSpec`? Here is a repo https://github.com/chicoxyzzy/proposal-reflect-tostringspec | Rationale | | There is no exact way to call spec's `ToString` in JS. | However it

Re: Reflect.toStringSpec proposal

> On Dec 13, 2016, at 4:51 PM, Sergey R wrote: > > I want to propose a new language feature — Reflect.toStringSpec. > Here is a repo https://github.com/chicoxyzzy/proposal-reflect-tostringspec > > Some context: >

Re: Ranges

Oh, I understood it. It looks like serious problem, but it is may not actually. If this spec change doesn't break web, we can introduce this idea? ___ es-discuss mailing list es-discuss@mozilla.org https://mail.mozilla.org/listinfo/es-discuss

Reflect.toStringSpec proposal

I want to propose a new language feature — Reflect.toStringSpec. Here is a repo https://github.com/chicoxyzzy/proposal-reflect-tostringspec Some context: https://github.com/airbnb/babel-plugin-dynamic-import-node/pull/2/ ___ es-discuss mailing list

Re: Ranges

On Tue, Dec 13, 2016 at 3:07 AM, Hikaru Nakashima wrote: > My idia is as follows: > > ``` > [1..5] //-> [1,2,3,4,5] > > (1..5) //-> iterate 1, 2, 3, 4, 5 > > > [1..Infinity] // -> TypeError because n > 2**32-1 > > (1..Infinity) // -> valid iterator > ``` As Andy

Re: Ranges

My idia is as follows: ``` [1..5] //-> [1,2,3,4,5] (1..5) //-> iterate 1, 2, 3, 4, 5 [1..Infinity] // -> TypeError because n > 2**32-1 (1..Infinity) // -> valid iterator ``` ___ es-discuss mailing list es-discuss@mozilla.org

RE: name anonymous functions on property assignments

About a year ago, Bergi asked[1] why no name is assigned to a function when it's created as part of an assignment to an object property: o.method = () => { }; Allen Wirfs-Brock replied: > We did not have consensus on doing the same for: > `MemberExpression.IdentifierName = FunctionExpression`

Membranes: filtering own properties, questions on ES7 intent

Hello, everyone. Now that the quarter at my local university is over, I'm working on my es7-membrane project again. [1] In implementing "filterOwnKeys", I realized I have wandered into a couple of open questions, where I do not know from the ES7 specification what the desirable behavior is. I