This edition
A journey through the origin of Async Rust, why it is necessary (and when it’s not) and the issues caused by the “over-async” phenomenon.
We will also cover why for library maintainers it’s hard to create sync/async public API for their crates and how (and whether) we can mitigate it.
Showcasing maybe-fut a library that with the power of advanced proc macro is able to allow developers to expose sync and async API reusing the same code.
Eventually, we’ll conclude with some thoughts on an async Rust std library and how the language could overcome code duplication when implementing both APIs.
LEVEL: Intermediate