|
@Carlos_Lande | |||||
|
I've been introducing myself to the world of fearless concurrency in rust and it's current state is a bit confusing. Futures 0.1, Futures 0.3, compat module, Tokio, std::future... Does this crate look like the final async/await proposal that end users will code with? Thanks!
|
||||||
|
||||||
|
async-std
@asyncrs
|
16. kol |
|
We're happy to announce the release of `async-std` beta to the public. `async-std` is a library that looks and feels like the @rustlang standard library, built from ground up for `async/await`.
async.rs/blog/announcin…
|
||
|
|
||
|
async-std
@asyncrs
|
17. kol |
|
async/await is just the syntax and will be the only that thing the Rust compiler ships.
This is our go at providing an approachable, consistent interface to learn on and understand things better.
|
||
|
|
||
|
async-std
@asyncrs
|
17. kol |
|
It's based on `std::future::Futures` and very little futures 0.3 only, no backwards compat shims.
|
||
|
|
||
|
Tokio
@tokio_rs
|
17. kol |
|
Tokio is moving to an async & await based API as well. See the latest examples here: github.com/tokio-rs/tokio…. This is available today in the 0.2.0-alpha.1 release. The announcement post is here: tokio.rs/blog/2019-08-a…
|
||
|
|
||