tokio-line does not compile
Closed this issue · 1 comments
nbigaouette commented
Here's the error I get on aa6948e:
cargo run --example echo
Compiling tokio-line v0.1.0 (file:///Users/nbigaouette/tokio-line.git)
src/low_level_transport.rs:2:5: 2:20 error: unresolved import `proto::pipeline`. There is no `pipeline` in `proto` [E0432]
src/low_level_transport.rs:2 use proto::pipeline;
^~~~~~~~~~~~~~~
src/low_level_transport.rs:2:5: 2:20 help: run `rustc --explain E0432` to see a detailed explanation
src/framed_transport.rs:6:5: 6:20 error: unresolved import `proto::pipeline`. There is no `pipeline` in `proto` [E0432]
src/framed_transport.rs:6 use proto::pipeline;
^~~~~~~~~~~~~~~
src/framed_transport.rs:6:5: 6:20 help: run `rustc --explain E0432` to see a detailed explanation
src/service.rs:2:5: 2:20 error: unresolved import `proto::pipeline`. There is no `pipeline` in `proto` [E0432]
src/service.rs:2 use proto::pipeline;
^~~~~~~~~~~~~~~
src/service.rs:2:5: 2:20 help: run `rustc --explain E0432` to see a detailed explanation
src/service.rs:6:5: 6:27 error: unresolved import `futures::stream::Empty`. There is no `Empty` in `futures::stream` [E0432]
src/service.rs:6 use futures::stream::Empty;
^~~~~~~~~~~~~~~~~~~~~~
src/service.rs:6:5: 6:27 help: run `rustc --explain E0432` to see a detailed explanation
src/client.rs:5:5: 5:20 error: unresolved import `proto::pipeline`. There is no `pipeline` in `proto` [E0432]
src/client.rs:5 use proto::pipeline;
^~~~~~~~~~~~~~~
src/client.rs:5:5: 5:20 help: run `rustc --explain E0432` to see a detailed explanation
src/client.rs:8:5: 8:27 error: unresolved import `futures::stream::Empty`. There is no `Empty` in `futures::stream` [E0432]
src/client.rs:8 use futures::stream::Empty;
^~~~~~~~~~~~~~~~~~~~~~
src/client.rs:8:5: 8:27 help: run `rustc --explain E0432` to see a detailed explanation
src/service.rs:45:25: 45:30 error: no method named `spawn` found for type `tokio::LoopHandle` in the current scope
src/service.rs:45 loop_handle.clone().spawn(move |_| {
^~~~~
error: aborting due to previous error
error: Could not compile `tokio-line`.
To learn more, run the command again with --verbose.
That's unfortunate as this repo should be, if I understand correctly, be a good entry point to learn how to use your own protocol with tokio (am I wrong?)
Could a travis ci be added to catch does out-of-sync api?
nbigaouette commented
I wrongly assumed tokio-line was using a Cargo.lock
file so when futures-rs
, tokio-core
, tokio-proto
and tokio-service
changes this one will break.
Until everything stabilize, I'm not sure there's an easy fix. Sorry for the noise!