Closed jamesray1 closed 4 years ago
This 'warning' is turned into an error in 'rustc' (with the current error-chain pkg in /src/vendor/error-chain). Thus, some versions of rustc even fail to build, because of this.
orig ref: https://twitter.com/ZschErik/status/1029062002109571073
Can you please double check which error-check versions are in your Cargo.lock?
I currently don't know anymore (I deleted the build 10 days ago), but I think it is in rustc-1.27.1 or 1.28.0 (build via gentoo portage ebuild), possible https://github.com/gentoo/gentoo/blob/master/dev-lang/rust/rust-1.28.0.ebuild. rustc-1.25.0 builds fine.
e.g. error-chain 0.11.0 works with rustc 1.25.0, but error-chain 0.11.0 in rustc 1.27.1-r2 (https://github.com/gentoo/gentoo/blob/master/dev-lang/rust/rust-1.27.1-r2.ebuild) doesn't work anymore.
0.12.0 should be fixing that, then: https://crates.io/crates/error-chain/0.12.0
@jamesray1 This issue can probably be closed.
OK, I have no need for varint ATM so CBB to try and test/reproduce.
These warnings still occur after adding
#[allow(renamed_and_removed_lints)]
: