Nailing object property order

Mark S. Miller erights at google.com
Thu Apr 16 17:13:40 UTC 2015


Developer productivity > hypothetical minor performance gains.

+1 to all steps to make the specified behavior more deterministic,
including this one.


On Thu, Apr 16, 2015 at 10:07 AM, liorean <liorean at gmail.com> wrote:

> I'm very much opposed to locking this down for general objects because
> it locks the implementation choices for generic objects down. What if
> the engine backing implementation was, say, some variation of a trie
> for instance? It cannot really be done today without adding extraneous
> data into the structure, because lookup in that case happens on a
> character by character basis, not on a whole string basis, so
> properties that use common prefixes would always end up adjacent and
> even if the keys weren't inserted in order by bit patterns into the
> trie as most implementations do, they would still be grouped by common
> prefix.
> --
> David "liorean" Andersson
> _______________________________________________
> es-discuss mailing list
> es-discuss at mozilla.org
> https://mail.mozilla.org/listinfo/es-discuss
>



-- 
    Cheers,
    --MarkM
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/es-discuss/attachments/20150416/9f048a93/attachment.html>


More information about the es-discuss mailing list