Comment #6 on issue 4168 by [email protected]: Array.of/from
use %AddElement unsafely
https://code.google.com/p/v8/issues/detail?id=4168
Not necessarily worrisome but very odd. It's basically calling SetElement
indicating that it doesn't want to follow prototype chains. That means it
will call a setter on the receiver if there is one, but not in the
prototype chain.
I'm in the process of rewriting SetElement etc with the lookup iterator,
and I basically don't have a replacement for this method since there's no
complete implementation of DefineProperty; and the current implementation
is wacky. The only thing that I think would make sense for now is having a
slow path for the non-default constructor.
For now I'm calling AddElement in my CL, which requires that the element
doesn't exist yet. That won't work for the non-default case in all cases...
--
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.
