Rust's Journey to Async/Await

Channel:InfoQ · Length:48:46 · Published:2019-11-11 · Views:89825

Watch on YouTube

Summary

Steve Klabnik walks through the history of Rust and how its design evolved toward async/await, including the alternatives tried and dropped. He also discusses the difficulty of adding a major feature to a language.

Why HN recommends it

HN points to it to show how deliberately the Rust team arrived at async/await and why it was chosen over alternatives like green threads.

It will show you how meticulous the core team is and how long it took to arrive at this incredible, best in class design. — HN, 2020

Programming language design · C, C++, Rust, Go & systems languages

Subtitles (excerpt)

hi everybody I'm Steve and this is rust journey to async/await I sort of been this theme have given a lot of talks about rustic Yukon and it seems like I'm always talking about something that's happening like three months in the future so this sort of continues on that trend of things you know as mentioned this is about how we arrived at a single weight and like the final couple little steps that are happening as well I'm giving this talk because I'm on the rust team in general I'm on the rust core team and in charge of the documentation team I work at CloudFlare although not on rust stuff doing two workshops tomorrow one on rust and helping out with one on cloud floor workers so I don't know if I'll see any there while I am on the rust team I want to emphasize that I was not like directly involved in all of this work I am primarily doing this as a like reporting capacity I like think of myself as like a amateur historian of rust development I like to keep track of how the language has evolved over time and sort of like deal with these major topics so I was not directly involved in the design I just read all the comments and talked to people over years so I'm kind of giving you my like semi outside perspective on how this went down

On Hacker News

Oh boy. The author of this post gave a speech about Rust’s journey to async/await: [VIDEO] I highly recommend you skim it. It will show you how meticulous the core team is and how long it took to arrive at this incredible, best in class design. — iknowstuff, 2020-04
Java is different. Tomcat's thread pool is the older way. A lot of newer stuff was using something promises-related instead with an event loop. But then recently Java added virtual threads which should obviate the need for that, similar to Go. Rust considered virtual threads but chose against that because it requires a more abstracted runtime like Java and Go have. Great preso on this [VIDEO] All… — traderj0e, 2026-05
As you probably know, Rust ended up with async/await. This video goes deep into that and the alternatives, and it changed my opinions a bit: [VIDEO] Golang differs from Rust by having a runtime underneath. If you're already paying for that, it's probably better to do greenthreading than async/await, which is what Go did. I still find the Go syntax for this more bothersome and error-prone, as you … — frollogaston, 2025-05
I believe these are the talks from Steve that he's referring to. It was enlightening for me: 1. Rust's Journey to Async/Await - [VIDEO] 2. The Talk You've been Await-ing for - [LINK] The first video goes into all the bits you're concerned about and all the things that Rust has tried before arriving where they are now — dwoot, 2020-12
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: [VIDEO] [LINK] — xiphias2, 2020-04

Related videos