On 2014/06/12 09:25:55, wingo wrote:
Hum, this points out a problem in the patch -- before, the set of
properties
in
an object was statically known, and so you could create a new object
literal
by
cloning a template and then updating properties that needed to be
computed at
runtime. Now with computed property names that isn't the case. In my
patch
we
still create a template for the first few properties -- the ones that
precede
any computed property name -- but subsequent properties are not in the
template.
This of course opens up the possibility of interference from
Object.prototype
:/
Hm, trying to understand what you mean. As far as the spec is concerned, all
properties are defined, not set, so the prototype should never interfere.
Are
you saying that it could yet potentially do in the current implementation?
https://codereview.chromium.org/332443002/
--
--
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.
