Open
Bug 1124876
Opened 10 years ago
Updated 1 month ago
Remove LookupProperty for name lookup and variable definition
Categories
(Core :: JavaScript Engine, defect)
Core
JavaScript Engine
Tracking
()
NEW
People
(Reporter: evilpie, Unassigned)
References
(Blocks 1 open bug)
Details
LookupNameNoGC, LookupNameWithGlobalDefault, LookupNameUnqualified, as well as DefFunOperation and DefVarOrConstOperation use LookupProperty.
I am not sure what kind of possible behaviors those functions have, i.e. only native objects? (probably no, because of DebugScopes?). It would be helpful if somebody pointed out the spec for those as well.
Reporter | ||
Comment 1•10 years ago
|
||
This is the last blocker to removing lookupProperty! I looked into this for a bit, but mapping ES6 references onto our LookupName/Fetch infrastructure is not necessarily obvious. Hopefully somebody comes along and fixes those, especially as we are not strictly ES6 compliant.
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•