Any plan to port std::sync::mpsc or other channel types?

[imtsuki]

Hi,

I'm trying replacing tokio with async-std in my own project and it's truly amazing. However there's no channel-equivalents like std::sync::mpsc in async-std, so I have to use the futures crate's version.

I think it would be very nice to have mpsc, oneshot, etc. from futures crate re-exported in this crate's namespace for consistency and convenience. Any plan for that?

[skade]

There is a plan! We're not quite sure though if we will ship it in this library or in a co-library. The channels module in libstd is widely considered a mistake, especially because there's reasons to use different channel implementations for different use-cases even in the same codebase.

[ghost]

I've started implementing an async version of crossbeam-channel, which will be separate from async-std, but belong in this Github organization.

[sdroege]

The channels module in libstd is widely considered a mistake, especially because there's reasons to use different channel implementations for different use-cases even in the same codebase.

Just for future reference: some of the concerns and a possible way forward for the std channel are in @stjepang's blog post about that here: https://stjepang.github.io/2019/03/02/new-channels.html

[ghost]

Closing in favor of #212

[ghost]

There is now a channel implementation in the master branch of async-std, behind the unstable flag:
#380