cargo fix - failure with Deserialize #5799
Description
Oh dear these issues sound bad! Are you sure you were testing with an up-to-date nightly? Recent changes in lint emissions should supress lints related to foreign macros (like derive in these cases) but if they’re still showing up that’s a bug!
Would you be able to share some test cases if it’s still showing problems?
#![feature(rust_2018_preview)] extern crate serde; #[macro_use] extern crate serde_derive; #[derive(Deserialize)] pub struct Struct(::module::Thing); mod module { #[derive(Deserialize)] pub struct Thing; }A complete source tree: deserialize-test-case.tar.gz
This test case will be "magically" fixed when the additions to the proc-macro crate wrapped by proc-macro2 become stable.
Output
warning: failed to automatically apply fixes suggested by rustc to crate `deserialize_test_case` after fixes were automatically applied the compiler reported errors within these files: * src/lib.rs This likely indicates a bug in either rustc or cargo itself, and we would appreciate a bug report! You're likely to see a number of compiler warnings after this message which cargo attempted to fix but failed. If you could open an issue at https://github.com/rust-lang/cargo/issues quoting the full output of this command we'd be very appreciative! warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition --> src/lib.rs:8:19 | 8 | pub struct Struct(::module::Thing); | ^^^^^^^^^^^^^^^ help: use `crate`: `crate::module::Thing` | = note: `-W absolute-paths-not-starting-with-crate` implied by `-W rust-2018-compatibility` = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition! = note: for more information, see issue TBD warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition --> src/lib.rs:7:10 | 7 | #[derive(Deserialize)] | ^^^^^^^^^^^ help: use `crate`: `crate::Deserialize` | = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition! = note: for more information, see issue TBD warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition --> src/lib.rs:8:19 | 8 | pub struct Struct(::module::Thing); | ^^^^^^^^^^^^^^^ help: use `crate`: `crate::module::Thing` | = note: `-W absolute-paths-not-starting-with-crate` implied by `-W rust-2018-compatibility` = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition! = note: for more information, see issue TBD warning: absolute paths must start with `self`, `super`, `crate`, or an external crate name in the 2018 edition --> src/lib.rs:7:10 | 7 | #[derive(Deserialize)] | ^^^^^^^^^^^ help: use `crate`: `crate::Deserialize` | = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition! = note: for more information, see issue TBD Finished dev [unoptimized + debuginfo] target(s) in 0.68s Tested on rustc 1.29.0-nightly (6a1c0637c 2018-07-23)