Comment #33 on issue 164 by charles.kendrick: Wrong order in Object properties interation
http://code.google.com/p/v8/issues/detail?id=164
Tim, the format I pointed out is likely to be adopted as the best alternative to the single-object format being used now because critically, it does not burn either one Object or one Array per value pair. It's routine for these lists to number in the hundreds or thousands, and for there to be many such lists in an application.
So, I'm afraid all my points stand: in a very very common use case, Chrome's choice of behavior puts developers in a position of severely degraded performance, or severely degraded expressiveness with moderately degraded performance.
About "how many more times" you need to point out the ECMA spec - the answer is none. We're all aware of it. It doesn't specify what to do, so Chrome can claim compliance while implementing either behavior.
There are extremely strong performance, backcompat and expressiveness arguments for providing order-preserving Objects, and no one cares about order-preserving Arrays, so it seems like the best implementation is pretty clear.
-- v8-dev mailing list [email protected] http://groups.google.com/group/v8-dev
