Update to tokio 1.0

[nickelc]

Draft until tokio-openssl, tokio-rustls and tokio-native-tls are ready.

• tungstenite: Update to bytes 1.0 snapview/tungstenite-rs#163
• tokio-rustls
• tokio-native-tls: tokio-native-tls: prepare v0.3.0 tokio-rs/tls#47
• tokio-openssl

[sdroege]

Thanks, I'll merge this once all the deps are on crates.io

[sdroege]

Also should wait for snapview/tungstenite-rs#163

[nickelc]

Also should wait for snapview/tungstenite-rs#163

nice to have but it's not required.

[sdroege]

nice to have but it's not required.

True, it doesn't involve API changes in tungstenite :)

[sdroege]

@nickelc Should we wait for the tungstenite release before releasing to crates.io or not? :)

[nickelc]

@nickelc Should we wait for the tungstenite release before releasing to crates.io or not? :)

tungstenite release could happen in hours or days and i don't expect big changes beside bytes 1.0.
I think updating tungsteniste in a patch release should be fine and would unblock other projects sooner.

[sdroege]

Let's do that then!

[sdroege]

Too bad, tungstenite was released as 0.12 now :)

[nickelc]

Too bad, tungstenite was released as 0.12 now :)

But updating to 0.12 in patch version should be ok because it's not in public, right?
And tokio 1.0 already bumped the MSRV to 1.45.

[sdroege]

But updating to 0.12 in patch version should be ok because it's not in public, right?

Well, it is:

async-tungstenite/src/lib.rs

Line 39 in 33e3722

pub use tungstenite;

Anyway, not much of a problem. Just means yet another release :)

[nickelc]

Well, it is:

async-tungstenite/src/lib.rs

Line 39 in 33e3722

pub use tungstenite;

my bad but 0.11 was fine. it unblocked a number of projects.

[sdroege]

Indeed :) I'll get a new release out some time later today