d at domenic.me
Thu Dec 4 15:21:20 PST 2014
From: Allen Wirfs-Brock [mailto:allen at wirfs-brock.com]
> Because some of the Array.prototype algorithms depend upon of the ability to an Array to dynamically grow its length or other characteristics that are not true of Typed Array instances. A new algorithm that is appropriate for a Typed Array implementation is specified for those cases. Otherwise, we just reference the Array.prototype algorithm.
Oh I see, that makes sense now that I realize how the return values of `map` and `filter` are created and filled. And yeah, agreed that the algorithm should be reusable for includes in particular.
> Add it to the existing proposal. It's an oversight that it wasn't included and something that should have been caught by reviewers if we were paying attention. In general, we want Array and Typed Arrays to support the same set of methods.
More information about the es-discuss