Comment #9 on issue 3394 by [email protected]: API should allow symbols as
property names
http://code.google.com/p/v8/issues/detail?id=3394
dcarney, you mentioned that it would be best to just change the accessor
API to remove the "name" argument, and thus solve this problem that way. I
implemented that on the API and runtime level -- storing a flag in the
ExecutableAccessorInfo to indicate whether the attached accessors had a
name or not -- but the codegen side is an unmitigated mess -- there are
seven architectures of platform-specific stubs, on the full-codegen side,
and then a bunch of hydrogen things too. Who knows what the TF impact may
be. There is a potential benefit to removing the name argument of course,
that it could speed up API access, but it's quite invasive. Do you still
think it's the way out here? If so, how to proceed? I wonder if we can
hydrogenate the callapigetter stub.
--
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.
