Domenic Denicola wrote:
> From: es-discuss [mailto:es-discuss-bounces at mozilla.org] On Behalf Of Adam Klein
>
>> >  Is there any reason not to specify some precondition checking in these algorithms and spec them to throw the RangeError without interacting with the elements of the array if it's known a priori that the resulting length will be>  2^32-1?
>
> ES6 adjusted the length limit upward to 2^53  - 1,  IIRC...

And yet Adam cited the draft ES6 HTML-formatted spec.

Seems like two problems:

* Error-checking after mutating -- in this case in ArraySetLength from 
Array [[DefineOwnProperty]] from Put 7(b)(v)(3) in 22.1.3.28 -- buried!

* The lack of 53-bit indexes, but isn't this waiting for a VM to try and 
see what breaks? Cc'ing Allen.

Buggy engines too, but perhaps their maintainers will want to wait a bit 
before fixing ;-).

/be

Domenic Denicola wrote:

> ES6 adjusted the length limit upward to 2^53  - 1,  IIRC...

And yet Adam cited the draft ES6 HTML-formatted spec.

Seems like two problems:

* Error-checking after mutating -- in this case in ArraySetLength from 
Array [[DefineOwnProperty]] from Put 7(b)(v)(3) in 22.1.3.28 -- buried!

* The lack of 53-bit indexes, but isn't this waiting for a VM to try and 
see what breaks? Cc'ing Allen.

Buggy engines too, but perhaps their maintainers will want to wait a bit 
before fixing ;-).