THE VIDEO SHELF · rust async
RustLatam 2019 - Without Boats: Zero-Cost Async IO
Without Boats, a Rust language team member, explains the design of Rust's async/await at RustLatam 2019. He covers the history and constraints behind zero-cost, allocation-free async state machines.
Why HN readers recommended it
Recommended during the await syntax debates for explaining the constraints that shaped Rust's async design.
This is a summary from the source dataset, not an endorsement by Hacker News or the video creator.
Video & recommendation details
- Creator / channel
- Rust Programming Language
- Topic
- rust async
- Format
- talk
- Level
- intermediate
- HN recommenders in dataset
- 5
- HN mentions in dataset
- 5
- Recommendation years in dataset
- 2019–2020
These counts and years describe the included Hacker News records; they are not YouTube views or the video’s publication date.
From the original HN conversations
Excerpts from the recorded comments. Follow each source for the full comment and surrounding discussion.
The nuances in this case went well beyond what I was expecting - it's actually more than just syntax, this heavily crosses over into semantics. It's been a very impressive process, and I was surprised at the power of the solution they landed on. - …
sgrove on Hacker News · 2019-05
In Update on await syntax in RustThat document isn't about arguing one way or the other, it lists all the different options and pros/cons. The post thread is the current stance of the lang team and letting everyone know they're going to make the final decision later this month. Boats' keynote …
holy_city on Hacker News · 2019-05
In A final proposal for Rust await syntaxI don't know anything about Kotlin, but if you are interested in the Rust story (history and evolution) this is an interesting talk: RustLatam 2019 - Without Boats: Zero-Cost Async IO [VIDEO]
AlexanderDhoore on Hacker News · 2019-10
In Why async fn in traits are hard
Summaries, classifications and recommendation records are from the HackerTube source dataset. Read about this library and its limitations.