Closed
Bug 1112564
Opened 10 years ago
Closed 8 years ago
for-in should only use the new iteration protocol
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 1246318
People
(Reporter: evilpie, Unassigned)
References
(Blocks 1 open bug)
Details
In bug 783829, to move forward we changed the js::IteratorMore code so that it allows both the old protocol (with StopIterator) and the new protocol with {value,done}. When we eventually remove __iterator__ and either remove Iterator and legacy generators or move them to the new protocol. Then we should be able to just use the new protocol.
|
Reporter | |
Updated•9 years ago
|
Summary: for-in should only use the new iteration protocol only → for-in should only use the new iteration protocol
|
|
Reporter | |
Comment 1•8 years ago
|
||
I am going to remove the new iteration protocol from IteratorMore, because it is not really required anymore.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•