-
Notifications
You must be signed in to change notification settings - Fork 288
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
Announce major Generator -> Coroutine rename #1155
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.
Seems ok!
Probably should mention that it's only relevant for nightly users. |
Updated. what do I need to do to publish this? |
Currently date is set for tomorrow, I can merge then (ping me). Or happy to publish today, but then date should be updated. |
huh... I... should probably not be writing blog posts at 2am... not sure why I used the 24th. @Mark-Simulacrum renamed the file to match today's date |
No, you definitely should, because this was super entertaining reading. Can you write all the Rust blog posts from now on? 😛 One question, though: you mentioned that generators are a convenient way to write iterators. Isn't there also a performance angle? For some reason I had the impression that the compiler-generated state machine would be faster than what, e.g., |
For a very simple |
cc rust-lang/rust#116447
cc rust-lang/rust#116958