On Sun 02 Mar 2014 04:18, Domenic Denicola dome...@domenicdenicola.com writes:
You can just do `if (Symbol.iterator in potentialIterable)`.
Of course, this can introduce time-of-check-to-time-of-use bugs.
Actually calling @@iterator on the iterable is more reliable.
Andy
Le 03/03/2014 10:11, Andy Wingo a écrit :
On Sun 02 Mar 2014 04:18, Domenic Denicola dome...@domenicdenicola.com writes:
You can just do `if (Symbol.iterator in potentialIterable)`.
Of course, this can introduce time-of-check-to-time-of-use bugs.
Actually calling @@iterator on the iterable is
Thanks for the pointer!
I like Claude's use-case and recall Allen citing it too. So, two reasons:
1. Higher-order functional programming wants a function, not literal syntax.
2. Subclassing Array works too, thanks to ES6's class-side inheritance.
/be
Rick Waldron
I'd like some help understanding why we are not using the word micro-tasks
here, and more generally why we are going our separate way and not trying to
unify with HTML. Here is my understanding:
- ES tasks are, essentially, purposefully under-specified versions of HTML
micro-tasks. (That is,
Is the function* syntax for generators final? I'm curious what the
justification for it is, but mostly I just need to know if it's likely to
change.
Thanks,
Joe
___
es-discuss mailing list
es-discuss@mozilla.org
On Mon, Mar 3, 2014 at 6:44 PM, joe joe...@gmail.com wrote:
Is the function* syntax for generators final?
Yes
I'm curious what the justification for it is,
The yield keyword was previously only reserved in strict mode (ES5
7.6.1.2), which means it's perfectly valid JS to have: function
On Mar 3, 2014, at 1:55 PM, Domenic Denicola wrote:
I'd like some help understanding why we are not using the word micro-tasks
here, and more generally why we are going our separate way and not trying to
unify with HTML. Here is my understanding:
I've specifically avoided the word
Is chore better than turn?
On Mar 3, 2014 4:10 PM, Allen Wirfs-Brock al...@wirfs-brock.com wrote:
On Mar 3, 2014, at 1:55 PM, Domenic Denicola wrote:
I'd like some help understanding why we are not using the word
micro-tasks here, and more generally why we are going our separate way
and
Are typed arrays considered to be part of ES6? I see they are described in
the ES6 working draft, but when I find lists of ES6 features on the web, I
never see those included. I see they are also described in a separate
specification here: http://www.khronos.org/registry/typedarray/specs/latest/
.
On Mar 3, 2014, at 4:32 PM, Mark S. Miller wrote:
Is chore better than turn?
Mark, to me turn, as a noun, sounds like a scheduling slot rather than the
thing that gets scheduled into the slot. For example: in the next turn, we
will run the handler for promise p. The thing that gets
On Mar 3, 2014, at 4:50 PM, Mark Volkmann wrote:
Are typed arrays considered to be part of ES6? I see they are described in
the ES6 working draft, but when I find lists of ES6 features on the web, I
never see those included. I see they are also described in a separate
specification here:
up ?
On Sun, Mar 2, 2014 at 5:43 PM, Andrea Giammarchi
andrea.giammar...@gmail.com wrote:
Brandon I take your answer as +1, thanks.
I've also gisted a possible/basic polyfill here:
https://gist.github.com/WebReflection/9317065
Cheers
On Sun, Mar 2, 2014 at 5:16 PM, Andrea Giammarchi
Allen Wirfs-Brock wrote:
Now its just a word that we are assigning our own meaning to, so we
can use turn if we want. But is that equivalence of turn and
task really what you're used to, and something whose meaning is
intuitive enough?
On naming, we can use Turn instead of Task if enough
13 matches
Mail list logo
