Comment #138 on issue 164 by [email protected]: Wrong order in Object
properties interation
https://code.google.com/p/v8/issues/detail?id=164
Just a quick note regarding #136 and #137: Trying to detect if the
iteration is "in order" doesn't make sense, this is only semidecidable from
the outside: By testing the result of a few iterations you may detect that
the underlying implementation doesn't return things in insertion order, but
you will never be able to prove that it will always obey that order.
In your example, it's e.g. easy to come up with hash functions/table sizes
which keep the illusion of obeying insertion order (whatever that means for
object literals).
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
---
You received this message because you are subscribed to the Google Groups "v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
