-
Notifications
You must be signed in to change notification settings - Fork 88
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
Add a story #68
Add a story #68
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.
Co-sign on this story, for sure. Thanks for writing this up.
Haha, I understood that async was still a bit too young and hard to document for inclusion in the book, but was still disappointed because there's very little that comes close to the book in terms of quality! But it's fantastic to hear that it might be included in the future ❤️ ! Definitely getting myself a third? edition once it's included! |
Niklaus was excited about [the RFC proposing that `block_on` be added to the stdlib][block-on-rfc], but understands that everyone is busy. However, if that RFC came to be, that would solve Niklaus' problems and make it more likely that `async` would be added to the documentation. Niklaus would really like to include `async` in a big update to the documentation that would likely happen with the Rust 2021 Edition. No pressure. | ||
|
||
[trpl]: https://doc.rust-lang.org/stable/book/ | ||
[people like Barbara]: https://github.com/rust-lang/wg-async-foundations/blame/5ce418ac4076850f515034010cc51b707441f695/src/vision/status_quo/barbara_makes_their_first_steps_into_async.md#L22 |
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.
Is this URL for [people like Barbara] right? It goes to a git-blame view, which seems a little unexpected.
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.
I was trying to highlight a particular section of that story of Barbara's, that's the only way I could figure out how to do it.
Perhaps not surprisingly, I see a parallel with #45. While Barbara in #45 might have the deep technical skills needed to write an async library that can be used across multiple runtimes, we could image someone like Alan trying to write their first async library and wanting it to be runtime-agnostic (perhaps because they might not have the necessary knowledge/experience to know how to pick a runtime to code against). Meanwhile Starol Klichols also wants to be able to write docs about async in a runtime-agnostic way. |
|
||
## The story | ||
|
||
Niklaus, who sometimes goes by the pen name "Starol Klichols", has authored some long-form documentation about Rust that people have found helpful. One could even go so far as to call this documentation a ["book"][trpl]. |
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.
these names 🤣
Niko told me to open this :P