(For the history of this thread to refer to it later) At the meeting it was decided not to remove `keys()` and `entries()`, and keep the `(value, againValue, set)` callback params signature.
The reasons: - Consistency with maps and to reuse callbacks from arrays; - Even if it may seem a "wrong" Set abstraction, it's too late to exclude from ES6. Dmitry On Tue, Oct 14, 2014 at 1:19 PM, Erik Arvidsson <[email protected]> wrote: > Removing Set.prototype.entries and Set.prototype.keys might make sense. > I'm not really sure why we added them. Probably for consistency. > > On Tue, Oct 14, 2014 at 2:42 PM, Axel Rauschmayer <[email protected]> > wrote: > >> Are we OK with this? Seems like removing `entries`, `keys` and providing >> own default `@@iterator` for `Set` which should be just `values()` would >> make it more sense from the abstraction usage perspective. >> >> >> W.r.t. your last suggestion: that’s how the spec does it. Anything else >> would definitely not have made sense. >> >> >> https://people.mozilla.org/~jorendorff/es6-draft.html#sec-set.prototype-@@iterator >> >> -- >> Dr. Axel Rauschmayer >> [email protected] >> rauschma.de >> >> >> >> >> _______________________________________________ >> es-discuss mailing list >> [email protected] >> https://mail.mozilla.org/listinfo/es-discuss >> >> > > > -- > erik >
_______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
