Not sure if this is sufficient motivation to accelerate the timeline for adding suitable parallels from Array.prototype, but it may be worth recalling what developers did last time there were obvious "gaps" in what a native prototype provided. Array#contains, anyone?
On Wed, Oct 1, 2014 at 3:28 PM, Axel Rauschmayer <[email protected]> wrote: > Then thing is: if we'd like to use maps for such use-case, it brings us > back to that inconvenient imperative style of assignments (even worse, > since you have to repeat that `.set(...)` constantly): > > ``` > var requestData = new Map(); > requestData.set(Names.ID, id); > requestData.set(Names.EMAIL, email); > requestData.set('needsReload', id); > ... > ``` > > > Note that you can chain: > > ```js > var requestData = new Map() > .set(Names.ID, id) > .set(Names.EMAIL, email) > .set('needsReload', id); > ``` > > Not too bad, IMO. > > -- > Dr. Axel Rauschmayer > [email protected] > rauschma.de > > > > > _______________________________________________ > es-discuss mailing list > [email protected] > https://mail.mozilla.org/listinfo/es-discuss > > -- Jeremy Martin 661.312.3853 http://devsmash.com @jmar777
_______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
