Through the Fire and the Flames
summary
Four concrete rules help decide whether to watch: the four recurring problems are Send and Sync, futures and await, lifetimes as a “consume by date”, and trait bounds. Expect explicit examples: Rc not Send nor Sync, mutex guard not Send, thread‑locals and Cell behaviors, and how Tokio uses tasks where you must spawn to get parallelism. The talk gives the two precise Send rules for futures (captured values and values held across await), explains nested future state machines, and shows when bounds must be repeated.
AI-written summary · about
chapters (7)
- 0:00Intro
- 2:24Send Bounds
- 9:24Futures
- 13:06The combinatorial problem
- 16:06Lifetimes
- 21:59Wear Bounds
- 25:56Where and Lifetimes
related talks
45mKeynote | Actors with Tokio – a lesson in ownership
30mBack to the Futures
29mAsychronous programming in Rust
18mA better way of doing Async Rust
30mDay2 02 Sean Klein
01h 01mThe Future of C++ Parallel and Concurrency Safety Guidelines
17mUsing !Send with the benefits of Send
26mReasoning with Async Rust