Rust has been gaining popularity recently atop of a simple promise: being as close to the hardware as C and C++, and yet somehow magically memory safe.

This safety comes from the strict enforcement of scope-based lifetimes. However, when writing asynchronous code, such enforcement becomes a lot harder.

Aside from that, Rust doesn't provide a standard runtime for asynchronous execution, relying instead on third parties like async-std, tokio and glommio.

This talk will approach the problem of how asynchronous Rust keeps its memory safety promises in the face of asynchronous execution, and explore the techniques used by the glommio runtime to make sure that this comes at minimum cost to system latencies