Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Proposal: rename next() #22

Open
Fishrock123 opened this issue Jun 5, 2019 · 2 comments
Open

Proposal: rename next() #22

Fishrock123 opened this issue Jun 5, 2019 · 2 comments

Comments

@Fishrock123
Copy link
Owner

Due to potential conflicts with iterator#next(), perhaps this part of the protocol should be renamed. Any thoughts?

Maybe something like give()?
@jasnell
Copy link
Contributor

jasnell commented Jun 6, 2019

give() works

@Fishrock123 Fishrock123 mentioned this issue Jul 23, 2019
Open
@Fishrock123
Copy link
Owner Author

My latest thought from this twitter thread was move() but I think give() is probably better.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jasnell @Fishrock123