Re: [heycam/webidl] Figure-out what supporting Array-subclassing implies (#345)

So at this point TypedOM is just using `iterable<>` and indexed getters/setters for its array-like interfaces, with the assumption that engines can optimize array-like accesses better than general proxies (which does seem to be the case in Blink and Gecko, at least).

This means that, per the current state of the world, the array-like interfaces still don't have access to any of the array *methods* - if you want to map over them, you still have to manually do `[...foo].map(...)`, rather than `foo.map(...)` directly. This is less than ideal, and I'd like to get this sort of thing fixed sooner rather than later.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/heycam/webidl/issues/345#issuecomment-361814861