On 2015/09/29 21:48:28, adamk wrote:
On 2015/07/18 07:59:19, Toon Verwaest wrote:
> What about setting a bit on symbols whether they are "absent on access
check
> failure", and extend GetProperty(Attributes)WithFailedAccessCheck to
also
handle
> such symbols in addition to all_can_read accessors and interceptors?
That
way
it
> becomes very easy to support a new symbol by just setting the bit, and
the
logic
> isn't spread throughout the system but localized to those 2 methods.
Caitlin, would you be interested in implementing Toon's suggestion here?
I'd
be
happy to pick it up myself.
I should add: it sounds to me like this is what SpiderMonkey is planning on
doing, and it it least works fine for @@isConcatSpreadable (not sure if it's
sufficient for @@toStringTag; depends on what behavior we want for toString
on
cross-domain frames).
https://codereview.chromium.org/1230793002/
--
--
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.
