Writing tokio code in rust has been difficult because of the Tokio Reform described in tokio.rs/blog/2018-02-tokio-… . The crate documentation doesn't clearly describe which crates are "old" and which are "new"... and mixing old and new leads to inscrutable error messages.

Mar 28, 2018 · 6:51 PM UTC

2
2
7
Replying to @davidbaron
I think, though, that tokio-core and tokio-io are old and busted, and the stuff in tokio::runtime and tokio::reactor are the new hotness?
1
The thing I'm working on depends on crates (like hyper) that depend on the old stuff, which means I can't use *any* of the new stuff, or things blow up ("what do you mean, that stream type doesn't implement Future?").
2
more replies
Replying to @davidbaron
I have experienced this too. Also, crates like tokio-serial are not compatible with thew new runtime stuff.