Please note it's unlikely this change will be reverted before the release.
This issue exists mostly to notify crate authors about the change.
In the next release of Rust, 1.27.0, a few lints will be renamed to be consistent with the other names and RFC 344. You can find the full rationale for the change and the list of changed lints in PR #50879.
Your crates have #[deny(warnings)] in the build, so the change broke their build. If you want to allow the lint while still supporting old compilers you can use:
#![allow(unknown_lints, renamed_and_removed_lints, old_lint, new_lint)]
Please note it's unlikely this change will be reverted before the release.
This issue exists mostly to notify crate authors about the change.
In the next release of Rust, 1.27.0, a few lints will be renamed to be consistent with the other names and RFC 344. You can find the full rationale for the change and the list of changed lints in PR #50879.
Your crates have
#[deny(warnings)]in the build, so the change broke their build. If you want to allow the lint while still supporting old compilers you can use: