iteration order for Object
charles at isomorphic.com
Thu Mar 10 17:44:52 PST 2011
separate OrderedObject wouldn't address most of the issues I've raised:
1. it would be no help to JSON - there would still be the severe expressiveness and object
allocation overhead I previously described
2. it would remain a surprising "gotcha" that numeric indices behave specially on Object
3. it would not address the backcompat issue with all the sites that depend on ordering
On 3/10/2011 5:00 PM, Jeff Walden wrote:
> Another idea might be to introduce OrderedObject or somesuch with guaranteed enumeration order.
> You might lose object literal support (although that could be readded), but that's the only
> loss that comes to mind after brief thought.
More information about the es-discuss