Closed Bug 881226 Opened 12 years ago Closed 12 years ago

Change {Array, Map, Set} iterator methods to mach the latest spec

Categories

(Core :: JavaScript Engine, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla27

People

(Reporter: sankha, Assigned: wingo)

References

(Blocks 1 open bug)

Details

(Keywords: dev-doc-complete, site-compat, Whiteboard: [DocArea=JS])

This is a follow up of bug 869996. Quoting Rick's comments in bug 869996, the spec had been changed for the iterator methods of Set. > Please see 15.16.6.2.2 SetIterator.prototype.next() of the latest > specification draft. > > .next() should produce an ItrResult object that has both a "value" and > "done" property. The "value" property's own value will be as those shown > above, the "done" property will be a boolean value that is |true| until > there are no more values to yield, at which time it will have the boolean > value |false| > > See line 14 comments, StopIteration has been removed from the design of the > feature
This actually applies to: ArrayIterator.prototype.next() MapIterator.prototype.next() SetIterator.prototype.next()
Summary: Change Set iterator methods to mach the latest spec → Change {Array, Map, Set} iterator methods to mach the latest spec
Blocks: es6
Blocks: 907717
I think this has been done for MapIterator and SetIterator objects? Wingo can you confirm? Then I'll make the changes accordingly in bug 894658 for ArrayIterator methods.
Flags: needinfo?(wingo)
As noted, see bug 919948.
Flags: needinfo?(wingo)
This has been fixed.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
For documentation purpose, in which release (and if possible in which bug to be able to access info in it).
Flags: needinfo?(sankha93)
This was done in bug 907077 for Sets, Maps and bug 919948 for the Array Iterators.
Flags: needinfo?(sankha93)
Assignee: general → wingo
No longer blocks: 907717
Depends on: 907717, 919948
Target Milestone: --- → mozilla27
Whiteboard: [DocArea=JS]
Reviewed, thanks :arai!
You need to log in before you can comment on or make changes to this bug.