Closed
Bug 628298
Opened 15 years ago
Closed 10 years ago
Implementing [[GetOwnProperty]] semantics
Categories
(Core :: JavaScript Engine, defect)
Core
JavaScript Engine
Tracking
()
RESOLVED
DUPLICATE
of bug 1122293
| Tracking | Status | |
|---|---|---|
| blocking2.0 | --- | .x+ |
People
(Reporter: igor, Unassigned)
Details
Currently in many places we have a pattern like:
obj->lookupProperty(&pobj);
if (not_found || obj != pobj) {
....
}
That is, we do the full prototype chain lookup only to treat the result as not-found if the property was not found in the original object. We should optimize that to avoid the useless prototype lookup.
|
Reporter | |
Updated•15 years ago
|
blocking2.0: betaN+ → ?
|
||
Updated•15 years ago
|
blocking2.0: ? → ---
|
||
Updated•15 years ago
|
blocking2.0: --- → .x
|
|
Reporter | |
Updated•13 years ago
|
Assignee: igor → general
|
Assignee | |
Updated•11 years ago
|
Assignee: general → nobody
|
||
Comment 5•10 years ago
|
||
Methods for GetOwnProperty are now present and non-own property lookups are almost removed (bug 1122293).
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•