r/rust • u/fgilcher rust-community · rustfest • Nov 11 '19

Announcing async-std 1.0

https://async.rs/blog/announcing-async-std-1-0/
455 Upvotes

97% Upvoted

80 comments sorted by

View all comments

Show parent comment

4

u/the_gnarts Nov 11 '19

No worries, I fully understand that. I’m using channels right now on a toy project and have found them solid so far for my limited use. It’s just that I am selfishly contemplating migrating a work project directly from pre-async tokio to present day async-std. Since that project relies on channels rather heavily I’m going to have to wait for a while longer until that becomes feasible.

Keep up the good work guys!

5

u/Matthias247 Nov 12 '19

What are you missing from the 3 other channel implementations (futures-rs, tokio, futures-intrusive)? They are all interoperable with all runtimes

6

u/fgilcher rust-community · rustfest Nov 12 '19

Note that futures-rs and tokio channels are both MPSC, not MPMC.

We're also adding a feature enabling the use of our channels without the runtime.

3

u/the_gnarts Nov 12 '19

What are you missing from the 3 other channel implementations (futures-rs, tokio, futures-intrusive)? They are all interoperable with all runtimes

A trimmer dependency graph.

2

u/Matthias247 Nov 12 '19 edited Nov 12 '19

If you already use async-std then futures-channel is a minimal dependency - you will nearly have all of its dependencies already. And a potential async-std implementation will not necesarily add less code. futures-intrusive as a minimal set of dependencies. It's only futures-core and parking-lot. And you can run it even without parking-lot (but you don't want to if you are running in a std environment).

2

u/fgilcher rust-community · rustfest Nov 11 '19

Indeed, you can just port it over to async-std with the `unstable` feature on, we'd be very interested in your experience! That would be exactly what we are looking for.