Allen Wirfs-Brock wrote:
ES5 didn't specify any precondition checks, so to do so now is, in theory, a
breaking change. In practice it might not matter, but nobody knows for sure.
Unlikely, given what Adam reported:
V8 properly throws a range error, but fails to move the element up one
index.
SpiderMonkey hangs (presumably because it has no special logic to deal
with very large, sparse arrays).
JSC throws an "Out of memory" Error and also fails to move the element
up one index.
Anyone care to test IE?
In practice, near the 2^31 - 1 maximum value for an arraylike's length,
there's no reliable interop today.
/be
_______________________________________________
es-discuss mailing list
[email protected]
https://mail.mozilla.org/listinfo/es-discuss
