Detached TypedArray access semantics
dehrenberg at chromium.org
Wed May 6 14:36:27 UTC 2015
In the draft ES6 spec, getting or setting array indices on detached
TypedArrays raises a TypeError. However, both V8 and SpiderMonkey seem to
return undefined from reads and silently succeed on writes. These semantics
have probably been shipping for some time.
As an implementer, I'm not sure what to do. Does anyone have any
information on whether it'd break the web to throw an error in this case?
What went into the decision to make these accesses throw an error in the
spec rather than the Chromium/Mozilla semantics? If it would break the web,
then should the spec be changed to match reality?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the es-discuss