Check out Dart's iterators

[Brendan Eich]

Oliver Hunt wrote:
> On Feb 11, 2013, at 1:29 PM, Brendan Eich<brendan at mozilla.com>  wrote:
>
>> Domenic Denicola wrote:
>>> From: es-discuss-bounces at mozilla.org [es-discuss-bounces at mozilla.org] on behalf of Oliver Hunt [oliver at apple.com]
>>>
>>>> For now I would say that we shouldn't expose the internal implementation behaviour of yield (which is what being able to explicitly create or call a generator produces).  That fairly trivially resolves the StopIteration behaviour by pushing it out of the ES6 spec.  If there's enough demand for manually creating or 'calling' a generator then we can fix it in ES6.x/7
>>> Would this prevent TaskJS from working in ES6?
>> Sorry, we are not going to do that.
>
> I still don't know what is being talked about here :D

That makes all of us :-P.

>> Oliver was around at at least one of the meetings where iterators got consensus or kept it. He's been AWOL enough that I'm going to say right here that he doesn't get to throw a veto.
>
> So what you're saying is that people who attend in person meetings are able to veto proposals,

No, I didn't say that. You are good at logic, I've seen your code. I 
know you grok P -> Q does not imply !P -> !Q.

>   and input from people who don't attend those meetings don't, and get much less input into the standard?  That's a fairly closed approach, especially when compared to more or less every other web standard.

We've been open on this stuff for years. Seven, by my count. You've been 
around enough of this, in person or on es-discuss, to participate.

> People aren't required to attend TPAC to have input at least considered for inclusion in W3 specs.

They don't get to throw unilaterla vetos there either.

/be