-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v0.1.x: Apply dyn
keywords to avoid fatal warnings on recent nightlies
#1351
Conversation
recent rust nightly started warning that not using `dyn` was deprecated. This requires MSRV 1.27.0+.
752b2eb
to
a81dab2
Compare
CI will fail on 1.26 (for no
error: unknown lint: `rust_2018_idioms`
--> tokio-executor/src/lib.rs:4:10
|
4 | #![allow(rust_2018_idioms)]
| ^^^^^^^^^^^^^^^^
|
note: lint level defined here
--> tokio-executor/src/lib.rs:1:54
|
1 | #![deny(missing_docs, missing_debug_implementations, warnings)]
| ^^^^^^^^
= note: #[deny(unknown_lints)] implied by #[deny(warnings)]
error: failed to parse manifest at `/home/david/src/tokio/tokio-macros/Cargo.toml`
Caused by:
editions are unstable
Caused by:
feature `edition` is required So it falls back to the question of the proposal MSRV. |
Note that when rust 1.37.0 (stable) is released in ~3 weeks, with the change to warn for lack of https://github.com/rust-lang/rust/blob/f2f4c0ed6c247eb8e94845c3e37eb6799ec74885/RELEASES.md |
CI now passing again, as merged in #1358. @LucioFranco are you good with this (to the extent that MSRV 1.31.0 is accepted) or would you prefer to keep all the warnings in output, but not fail, as in #1368? |
@dekellum hey sorry for the delay on this! I've been quite swamped at work and we really want to get the first few alpha versions out. I want you to know I'm not ignoring this at all! I am going to try to give this and the other PRs reviews once we get the alphas out in the next few days. Let me know if you need anything. And again sorry its taking this long 😭 |
This is part (1) of proposed changes in #1348. It may need to wait for stronger motivation, but I wanted to make the changes available. This depends on an MSRV of at least 1.27.0.
Motivation
On the v0.1.x branch, the use of
#[deny(warnings)]
makes the following warnings fatal on recent nighty compilers (in my case currently: rustc 1.38.0-nightly (83e4eed16 2019-07-14)), when building a local git tree.When built as a dependency of a normal application, cargo passes
--cap-lints=allow
to rustc (or forcargo -vv
,--cap-lints=warn
at most), so these are not fatal in that case. The current azure-pipelines CI appears to only test with stable rust (e.g. 1.36.0) or older nightlies, so this hasn't broken CI, yet.Solution
I applied
cargo fix
followed bycargo fmt
and then filtered through the changes (git add --patch
) to isolate thesedyn
additions.Also this bumps the check-minrust MSRV to 1.27.2, just to hopefully to get CI passing.