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
{{ message }}
Repository navigation
Cannot add an exception to #[deny(lint group)] with #[warn(specific lint)] #41941
Actual result with rustc 1.19.0-nightly (978d2cf 2017-05-10): hard error:
error: floating-point literals cannot be used in patterns
--> a.rs:5:12
|
5 | iflet0.0 = 1.0{}
| ^^^
|
= note: #[deny(illegal_floating_point_literal_pattern)] implied by #[deny(warnings)]
= warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
= note:for more information, see issue #41620 <https://github.com/rust-lang/rust/issues/41620>
note: lint level defined here
--> a.rs:1:9
|
1 | #![deny(warnings)]
| ^^^^^^^^
ERROR:rustc_lint::builtin: span mc spanspam
error: aborting due to previous error
Note that allowcan add an exception, but of course it makes the warning not be shown at all:
Triage: This was discussed by the language team here , and it was decided that the current behavior should be kept, but that the documentation should be updated to clarify the situation.
The documentation was updated in this PR. After some iteration over the years, we now have this wording:
Lint Group: warnings - All lints that are set to issue warnings
That makes the current behavior match the docs, so let's close as fixed.
Activity
oli-obk commentedon May 15, 2017
related: #34596
Enselic commentedon Sep 27, 2023
Triage: This was discussed by the language team here , and it was decided that the current behavior should be kept, but that the documentation should be updated to clarify the situation.
The documentation was updated in this PR. After some iteration over the years, we now have this wording:
That makes the current behavior match the docs, so let's close as fixed.