Proposal: rename `next()`

Fishrock123 / bob

🚰 binary data "streams+" via data producers, data consumers, and pull flow.

MIT License

79 stars 8 forks source link

Open Fishrock123 opened 5 years ago

Fishrock123 commented 5 years ago

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

Maybe something like give()?

jasnell commented 5 years ago

give() works

Fishrock123 commented 5 years ago

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