On Oct 25, 2014, at 1:32 PM, Brendan Eich wrote:

> Allen Wirfs-Brock wrote:
>> On Oct 24, 2014, at 9:11 AM, Brendan Eich wrote:
>> 
>>> >  André Bargull wrote:
>>>> >>  IE11 moves elements up one index, throws a RangeError and completes instantly (no hang or oom).
>>> >  >  Per spec, huzzah -- but the spec needs fixing.
>> 
>> That conclusion isn't so obvious to me.
> 
> The spec bugs is the buried throw after mutation. That's obvious in hindsight.

Arguably a design bug, rather than a spec. bug.  But I'm assuming that who ever originally wrote up these algorithms were being intentional about such things.

There are a number of places int he ES6 spec. where throws occur after mutation (and Proxy introduces the possibility of a lot more).  What we have been trying to do in both the ES5 and ES6 spec. is to improved expected interoperability  by being more explicit about exception ordering regardless of whether pre or post mutation).

Allen

Arguably a design bug, rather than a spec. bug.  But I'm assuming that who ever originally wrote up these algorithms were being intentional about such things.

There are a number of places int he ES6 spec. where throws occur after mutation (and Proxy introduces the possibility of a lot more).  What we have been trying to do in both the ES5 and ES6 spec. is to improved expected interoperability  by being more explicit about exception ordering regardless of whether pre or post mutation).