Status: Assigned
Owner: [email protected]
CC: [email protected], [email protected], [email protected],
[email protected]
Labels: Type-Bug Priority-Medium Harmony
New issue 4081 by [email protected]: Make [[HomeObject]] a lexically scoped
binding?
https://code.google.com/p/v8/issues/detail?id=4081
[[HomeObject]] could be lexically bound now that we removed toMethod in ES6
but
it would require that we add an extra scope around object literals.
Today:
let o = {
m() { super.toString }
};
becomes something like:
let o = {
m() {
LookupSuperProperty(this, %ThisFunction().[[HomeObject]], 'toString') }
};
o.m.[[HomeObject]] = o;
Which we could change to:
let o;
{
let home_object;
o = {
m() { LookupSuperProperty(this, home_object, 'toString') }
}
home_object = o;
}
and similarly with classes. Classes are simpler because they already have a
scope.
Concerns: toMethod might come back with a vengeance.
--
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.
