Closed
Bug 1485452
Opened 6 years ago
Closed 6 years ago
Remove IsPropertyIterator / isLegacyIterator?
Categories
(Core :: JavaScript Engine, enhancement)
Core
JavaScript Engine
Tracking
()
RESOLVED
FIXED
mozilla64
People
(Reporter: anba, Assigned: khyperia)
Details
Attachments
(1 file)
I don't think |PropertyIteratorObject| can be exposed to client-code anymore, which means |js::IsPropertyIterator| (vm/Iterator.{h,cpp}) and IsLegacyIterator (builtin/TestingFunctions.cpp) can be removed.
Assignee | ||
Comment 1•6 years ago
|
||
Assignee | ||
Updated•6 years ago
|
Assignee: nobody → khyperia
Status: NEW → ASSIGNED
Comment 2•6 years ago
|
||
anba: if you could make a Phabricator account soon that would be great, because you were the original reviewer :)
Comment 3•6 years ago
|
||
Comment on attachment 9006300 [details] Bug 1485452 - Remote IsPropertyIterator/IsLegacyIterator. Jan de Mooij [:jandem] has approved the revision.
Attachment #9006300 -
Flags: review+
Assignee | ||
Updated•6 years ago
|
Keywords: checkin-needed
Pushed by apavel@mozilla.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/d3abd725b443 Remote IsPropertyIterator/IsLegacyIterator. r=jandem
Keywords: checkin-needed
Comment 5•6 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/d3abd725b443
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
status-firefox64:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla64
Updated•6 years ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•