Shouldn't those be implemented in `%IteratorPrototype%` instead, so they can be used across all iterator types (including array entries, set entries, generator instances, etc.)?
On Fri, Dec 9, 2016, 15:53 Dmitry Soshnikov <[email protected]> wrote: > There are some good examples with `MapIterator`, and its `filter`, `map`, > `collect` or `collectAs` final methods here (from some old discussion): > https://github.com/rwaldron/tc39-notes/blob/master/es6/2014-11/nov-19.md#58-mapprototypemap-and-mapprototypefilter-spec--set > I'm pretty sure there should've been other discussions on this, but I'm not > sure about current state. > > Just build a working prototype library from those examples as a proof on > concept. Then spec'ing it should be relatively easy after it (assuming a > champion who will be willing to run it through). > > > Dmitry > > On Fri, Dec 9, 2016 at 7:46 AM, Benjamin Gruenbaum <[email protected]> > wrote: > > Hey, > > I remember a lot of talk about adding `.map/.filter` etc to iterators. The > benefits of doing this are pretty big and I think fairly well understood > and several other proposals (like observables and async iterators) would > benefit from it. > > (I expand on the big advantages this has over Array#map/filter if needed). > > Is anyone currently working on such a proposal? Was it discussed? > > I'd really like to see it move forward. > > Cheers > > _______________________________________________ > es-discuss mailing list > [email protected] > https://mail.mozilla.org/listinfo/es-discuss > > > _______________________________________________ > es-discuss mailing list > [email protected] > https://mail.mozilla.org/listinfo/es-discuss >
_______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
