On 7/29/2013 1:29 PM, Brendan Eich wrote:
>
> More recently, Jason implemented 'iterator' for two reasons, I think: 
> 1, lack of symbol spec of implementation as prerequisite; 2, belief 
> that a public name was better. Jason argued that case here, but I 
> don't think he prevailed (Dean Landolt disagreed).
>
> We aren't putting this out "in the wild" for use by anyone, it's just 
> a temporary state, which depends on symbol spec resolution for ES6 -- 
> this thread's topic!

Right, I should have been explicit. It's definitely a temporary measure. 
Similarly, V8 does some non-spec stuff to make for-of work (I think it 
just assumes the object is already an iterator). I just meant it as an 
example of a protocol in action (even if as a temporary stopgap).

Right, I should have been explicit. It's definitely a temporary measure. 
Similarly, V8 does some non-spec stuff to make for-of work (I think it 
just assumes the object is already an iterator). I just meant it as an 
example of a protocol in action (even if as a temporary stopgap).