Never snooze a future
Summary
This article argues that snoozing a future is a bug in async Rust, leading to deadlocks or 'futurelocks' in patterns like select!, streams, and buffered futures. It surveys multiple deadlock scenarios, contrasts async control flow with traditional threading, and discusses remedies such as owning futures, avoiding pinning in async functions, and exploring new concurrency helpers like join_me_maybe and Moro. The piece concludes with a practical rule: don’t snooze a future.