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
$ cargo --version
cargo 1.42.0 (86334295e 2020-01-31)
$ git rev-parse --short HEAD
9682623
$ cargo build
Compiling multiaddr v0.3.1 (/Users/jameshageman/Documents/Github/school/fydp/rust-multiaddr)
warning: trait objects without an explicit `dyn` are deprecated
--> src/errors.rs:13:22
|
13 | ParsingError(Box<error::Error + Send + Sync>),
| ^^^^^^^^^^^^^^^^^^^^^^^^^^ help: use `dyn`: `dyn error::Error + Send + Sync`
|
= note: `#[warn(bare_trait_objects)]` on by default
warning: trait objects without an explicit `dyn` are deprecated
--> src/errors.rs:34:32
|
34 | fn cause(&self) -> Option<&error::Error> {
| ^^^^^^^^^^^^ help: use `dyn`: `dyn error::Error`
warning: use of deprecated item 'std::error::Error::description': use the Display impl or to_string()
--> src/errors.rs:18:21
|
18 | f.write_str(error::Error::description(self))
| ^^^^^^^^^^^^^^^^^^^^^^^^^
|
= note: `#[warn(deprecated)]` on by default
error[E0277]: the trait bound `cid::Error: std::error::Error` is not satisfied
--> src/errors.rs:50:33
|
50 | Error::ParsingError(err.into())
| ^^^^ the trait `std::error::Error` is not implemented for `cid::Error`
|
= note: required because of the requirements on the impl of `std::convert::From<cid::Error>` for `std::boxed::Box<dyn std::error::Error + std::marker::Send + std::marker::Sync>`
= note: required because of the requirements on the impl of `std::convert::Into<std::boxed::Box<dyn std::error::Error + std::marker::Send + std::marker::Sync>>` for `cid::Error`
error: aborting due to previous error
For more information about this error, try `rustc --explain E0277`.
error: could not compile `multiaddr`.
To learn more, run the command again with --verbose.
Just thought I'd flag the build failure - it looks like #37 is addressing it.
The text was updated successfully, but these errors were encountered:
Just thought I'd flag the build failure - it looks like #37 is addressing it.
The text was updated successfully, but these errors were encountered: