Why asynchronous Rust doesn't work

1. rfcs

   1 688 6,144 9.3 Markdown

   RFCs for changes to Rust

   

   Rust did have green threading (user threads and goroutines) runtime back before the v1.0 stabilization but they removed it to make the language applicable to a broader range of problems.

2. InfluxDB

   www.influxdata.com featured

   InfluxDB – Built for High-Performance Time Series Workloads. InfluxDB 3 OSS is now GA. Transform, enrich, and act on time series data directly in the database. Automate critical tasks and eliminate the need to move data externally. Download now.

   

3. embassy

   2 85 6,757 9.9 Rust

   Modern embedded framework, using Rust and async.

   

   Rust’s async design allows for async to be used on a variety of hardware types, like embedded. Green threads/fibers are much more useful for managed languages like Go and Java that don’t typically have to run without an operating system or without a memory allocator. Of course C++ can do this also, with their new coroutines/generators feature but I don’t think it’s very controversial to say that it is much harder to use than Rust’s async.

4. async-std

   3 20 4,037 5.5 Rust

   Async version of the Rust standard library

   

   Go's solution is for the scheduler to notice after a while when a goroutine has blocked execution and to shift goroutines waiting their turn to another thread. async-std pondered a similar approach with tasks, but it proved controversial and was never merged.

Suggest a related project