Dev.to
5/9/2026

From Spawn to FuturesUnordered: How Community Feedback Reshaped Our Async Design
Short summary
After Reddit feedback, the author reconsiders cross-platform Rust async runtime design. Rather than optimizing for Tokio and patching single-threaded platforms with workarounds, they propose FuturesUnordered for task initialization—eliminating unsafe code, trait coupling, and platform-specific hacks while maintaining uniform behavior across Tokio, Embassy, and WASM.
- •Community feedback revealed Spawn trait was unnecessary for single-threaded platforms, solving problems created by the design itself
- •FuturesUnordered approach eliminates unsafe code, type-erased boxing, and platform-specific workarounds while supporting all platforms identically
- •Core lesson: design from each platform's constraints outward, building abstraction at the intersection—not top-down from the richest platform
Generated with AI, which can make mistakes.
Is this a good recommendation for you?


