You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, hyper 0.12 is waiting for the release of futures 0.2. Tokio has explicitly supported the work-steal thread pool.
I also hope that this crate can use features to select whether the client uses asynchronous mode, that is say that support synchronous and asynchronous at the same time, the default synchronization mode.
However, currently, Rust/Cargo doesn't support two versions of a library at the same time, which makes it very difficult for me to do it. Maybe 2018-epoch RFC can help me?
Maybe use reqwest? But it currently only supports uses system-native TLS....
Or wait for hyper 0.12 to give up sync mode directly?
The text was updated successfully, but these errors were encountered:
futures 0.3 (alpha) support was just added to the master branch of hyper. E.g. see this for an example of a client using Futures + await. I think it would be great to use this.
hyperium/hyper#1443
Currently, hyper 0.12 is waiting for the release of futures 0.2. Tokio has explicitly supported the work-steal thread pool.
I also hope that this crate can use features to select whether the client uses asynchronous mode, that is say that support synchronous and asynchronous at the same time, the default synchronization mode.
However, currently, Rust/Cargo doesn't support two versions of a library at the same time, which makes it very difficult for me to do it. Maybe 2018-epoch RFC can help me?
Maybe use reqwest? But it currently only supports uses system-native TLS....
Or wait for hyper 0.12 to give up sync mode directly?
The text was updated successfully, but these errors were encountered: