Feat migrate tokio

[dizda]

No description provided.

[link2xt]

@dizda What is the rationale for this? Why is this needed and why this isn't at least a feature that can be enabled/disabled?

We have recently added a dependency of fast-socks5 to https://github.com/async-email/async-smtp, https://github.com/async-email/async-imap and https://github.com/deltachat/deltachat-core-rust/, and so far deltachat-core-rust doesn't depend on tokio, only async-std.

cc @dignifiedquire, @Jikstra

[dizda]

Hey @link2xt,

It seems that async-std is not really maintained anymore...
While Tokio's project is pretty active.
We've made the decision to move away from async-std, and as some Traits of Tokio 1.0 will be merged into std, we've made the decision to move that library completely to Tokio.

If you're willing to make a feature to switch libraries, feel free to do so.
Or you could use this Trait to switch convert your traits https://github.com/tokio-rs/tokio/blob/e31e06c5c220ed986b3809d7a69c77c8d828ca2c/tokio-util/src/compat.rs

[Jikstra]

@link2xt i'm not too deep in the rust ecosystem/community, is that the case that async-std is not really maintained anymore?

[dizda]

You can have a glimpse:

https://github.com/tokio-rs/tokio/commits/master

vs

https://github.com/async-rs/async-std/commits/master

[dignifiedquire]

Project status for async-std: async-rs/async-std#992 (comment)

Tldr: it is still maintained and used in a lot of projects.