cargo build fails with compiler error

[stevej]

While attempting to build from a clean branch, I've run into a compile-time error complaining about a double import error.

/Users/stevej/src/grpc-rust% cargo clean                                                       (git)-[master]
/Users/stevej/src/grpc-rust% cargo version                                                     (git)-[master]
cargo 0.13.0-nightly (eca9e15 2016-11-01)
/Users/stevej/src/grpc-rust% cargo build                                                       (git)-[master]
   Compiling cfg-if v0.1.0
   Compiling crossbeam v0.2.10
   Compiling void v1.0.2
   Compiling semver v0.1.20
   Compiling protobuf v1.0.24 (http://github.com/stepancheg/rust-protobuf#dd1b66ae)
   Compiling log v0.3.6
   Compiling futures v0.1.6
   Compiling hpack v0.3.0
   Compiling core-foundation-sys v0.2.2
   Compiling libc v0.2.18
   Compiling bitflags v0.4.0
   Compiling lazycell v0.4.0
   Compiling solicit-fork v0.4.4 (http://github.com/stepancheg/solicit.git#b8a5030e)
   Compiling net2 v0.2.26
   Compiling rustc_version v0.1.7
   Compiling core-foundation v0.2.2
   Compiling security-framework-sys v0.1.9
   Compiling nix v0.7.0
   Compiling security-framework v0.1.9
   Compiling slab v0.3.0
   Compiling scoped-tls v0.1.0
   Compiling num_cpus v1.2.0
   Compiling futures-cpupool v0.1.2
   Compiling mio v0.6.1
   Compiling tokio-core v0.1.1
   Compiling tokio-tls v0.1.0 (https://github.com/tokio-rs/tokio-tls/#3d49e52e)
   Compiling grpc v0.0.2 (file:///Users/stevej/src/grpc-rust)
error[E0252]: a trait named `Stream` has already been imported in this module
 --> src/futures_misc/stream_merge2.rs:2:5
  |
1 | use futures::*;
  |     ----------- previous import of `Stream` here
2 | use futures::stream::Stream;
  |     ^^^^^^^^^^^^^^^^^^^^^^^ already imported

error: aborting due to previous error

error: Could not compile `grpc`.

[stevej]

I don't see this error in CI and so I suspect our build environments are not the same. Are you building with rust 1.13.0?

[stepancheg]

I reproduced it locally. Will fix it now.