On 7/23/15 7:29 AM, Paolo Amadini wrote:
Well, I was thinking more of something built-in, other than Iterator,
to achieve the same effect over a data structure (for example something
that could be provided from elsewhere as an argument).
Paolo,
I might be missing something, but why is __iterator__ and the
nonstandard iteration protocol needed for this?
But apparently I'm stuck with iterating over keys and reading values
separately, or
implementing my version of Iterator (at which point I don't see why
I shouldn't simply use Iterator in privileged code
I don't think anyone on the SpiderMonkey end particularly cares whether
Iterator or some replacement is used. What the SpiderMonkey team cares
about is that the old iteration protocol not be used. Does that make
sense? And the reason they would like it to not be used is that it's
not compatible with the ES6 protocol to such an extent that we can't fix
some of our spec-compliance bugs without removing it. As in, there are
some places in the code where SpiderMonkey ends up having to guess which
iteration protocol is being used, and it can't always guess correctly...
-Boris
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
