-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Normative Conventions: pretend primitives aren't iterable #152
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🎉
Gotta do that followup to add .codepoints()
and/or similar methods for getting iterators though.
1627148
to
d428162
Compare
I think we could probably get away with also changing |
|
Possibly worth calling out that this applies to async-iterable-taking positions as well. |
311e718
to
a73fa06
Compare
@syg I've added the enumeration of all positions where primitives are currently iterated. Please review. |
Co-authored-by: Kevin Gibbons <[email protected]>
We discussed this in the June plenary while considering iterator helper follow-on proposals. While we didn't call for consensus on it, there were many voices in support of this and none opposed. I will propose we officially adopt it at an upcoming plenary.