Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
method
vs the first-class type (tc39/proposal-iterator.range#22):I'm preferring the current method semantics to a first-class type (
Range
class).The method semantics is much JS style and provides a much clear API.
If @rbuckton is strongly requiring the first-class type please leave a comment.
reusable semantics (tc39/proposal-iterator.range#17):
In the April meeting there are two kinds of ideas
iterator + non-reusable
/first-class + reusable
, I choose the prior one. In the after discussions in tc39/proposal-iterator.range#17, I think non-reusable is a very natural idea for an iterator so I leave it as-is.If @sffc and @littledan gonna block this due to the non-reusable semantics, please leave a comment.
If there are no blocking reasons, I think it has met the stage 2 entrance criteria.