HackerTube

RustLatam 2019 - Without Boats: Zero-Cost Async IO

Rust Programming Language5 HN recommenders · 2019–2020
55K views · talk · dated · Uploaded 2019-04-22

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.

Recommended during the await syntax debates for explaining the constraints that shaped Rust's async design.

C, C++, Rust, Go & systems languagesProgramming language design

Watch on YouTube

5 comments from Hacker News

@holy_city2019 · in “A final proposal for Rust await syntax”

That 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 at rust-latam goes into some more detail as well. [VIDEO] I'm just a casual observer here, but it seems like just about every argument and position on the subject has been iterated across Github, internals.rust-lang.org, the IRC/Discourse/Zulip chats, Reddit, and now HN. This post by boats is just the next stepping stone alerting the community to the direction the team is leading and that it's going to be over soon.

RecommendsView on HN
@sgrove2019 · in “Update on await syntax in Rust”

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. - Rust has to find a syntax that can work with different underlying libraries (Rust can compile to lots of different targets, some will have capability to accommodate larger libraries than others) - The abstraction can't incur undue overhead (callback-based solutions may cause allocations that are hard to keep under control and will split the language if it spreads too much) - The syntax should be pleasant to write for at least the majority of people (modeling your entire application as a state machine around async computation is pretty unpleasant) - The compiler has to be able to give helpful error messages (this was a problem early on I think) - Language authors had to think about how the borrow checker would work across async points, and whether to invest in changing the language to make that possible. - and so on and so on I really loved this talk by Without Boats (the author of the friendly article) going over all this stuff, really gave me a good sense of what they were up against [VIDEO]

Strongly recommendsView on HN
@AlexanderDhoore2019 · in “Why async fn in traits are hard”

I 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]

RecommendsView on HN
@teddyc2019 · in “Ask HN: Best Talks of 2019?”

I thought this talk about Async in Rust was pretty cool (RustLatam 2019 - Without Boats: Zero-Cost Async IO): [VIDEO]

RecommendsView on HN
@xiphias22020 · in “I can't keep up with idiomatic Rust”

I was referring to the fact that it is the only async implementation that I know of that compiles to a state machine that doesn't need to allocate new memory for each continuation. I think it will translate to extremely fast web services in practice. Pinning is of course part of the elegant solution. There are some great videos about it: [LINK] [VIDEO]

RecommendsView on HN