rust/tests/ui/lint/issue-70819-dont-override-forbid-in-same-scope.stderr

error: deny(unused) incompatible with previous forbid
  --> $DIR/issue-70819-dont-override-forbid-in-same-scope.rs:21:13
   |
LL |     #![forbid(unused)]
   |               ------ `forbid` level set here
LL |     #![deny(unused)]
   |             ^^^^^^ overruled by previous forbid
   |
   = 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 #81670 <https://github.com/rust-lang/rust/issues/81670>
note: the lint level is defined here
  --> $DIR/issue-70819-dont-override-forbid-in-same-scope.rs:17:11
   |
LL | #![forbid(forbidden_lint_groups)]
   |           ^^^^^^^^^^^^^^^^^^^^^

error: aborting due to 1 previous error
introduce future-compatibility warning for forbidden lint groups We used to ignore `forbid(group)` scenarios completely. This changed in #78864, but that led to a number of regressions (#80988, #81218). This PR introduces a future compatibility warning for the case where a group is forbidden but then an individual lint within that group is allowed. We now issue a FCW when we see the "allow", but permit it to take effect. 2021-01-30 00:06:00 +00:00			`error: deny(unused) incompatible with previous forbid`
			`--> $DIR/issue-70819-dont-override-forbid-in-same-scope.rs:21:13`
Prevent forbid from being ignored if overriden at the same level. That is, this changes `#[forbid(foo)] #[allow(foo)]` from allowing foo to forbidding foo. 2020-06-15 18:17:35 +00:00			`\|`
			`LL \| #![forbid(unused)]`
			\| ------ `forbid` level set here
			`LL \| #![deny(unused)]`
Use true previous lint level when detecting overriden forbids Previously, cap-lints was ignored when checking the previous forbid level, which meant that it was a hard error to do so. This is different from the normal behavior of lints, which are silenced by cap-lints; if the forbid would not take effect regardless, there is not much point in complaining about the fact that we are reducing its level. It might be considered a bug that even `--cap-lints deny` would suffice to silence the error on overriding forbid, depending on if one cares about failing the build or precisely forbid being set. But setting cap-lints to deny is quite odd and not really done in practice, so we don't try to handle it specially. This also unifies the code paths for nested and same-level scopes. However, the special case for CLI lint flags is left in place (introduced by #70918) to fix the regression noted in #70819. That means that CLI flags do not lint on forbid being overridden by a non-forbid level. It is unclear whether this is a bug or a desirable feature, but it is certainly inconsistent. CLI flags are a sufficiently different "type" of place though that this is deemed out of scope for this commit. 2020-11-07 23:14:38 +00:00			`\| ^^^^^^ overruled by previous forbid`
introduce future-compatibility warning for forbidden lint groups We used to ignore `forbid(group)` scenarios completely. This changed in #78864, but that led to a number of regressions (#80988, #81218). This PR introduces a future compatibility warning for the case where a group is forbidden but then an individual lint within that group is allowed. We now issue a FCW when we see the "allow", but permit it to take effect. 2021-01-30 00:06:00 +00:00			`\|`
bless ui tests 2022-09-18 15:55:36 +00:00			`= 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 #81670 <https://github.com/rust-lang/rust/issues/81670>`
introduce future-compatibility warning for forbidden lint groups We used to ignore `forbid(group)` scenarios completely. This changed in #78864, but that led to a number of regressions (#80988, #81218). This PR introduces a future compatibility warning for the case where a group is forbidden but then an individual lint within that group is allowed. We now issue a FCW when we see the "allow", but permit it to take effect. 2021-01-30 00:06:00 +00:00			`note: the lint level is defined here`
			`--> $DIR/issue-70819-dont-override-forbid-in-same-scope.rs:17:11`
			`\|`
			`LL \| #![forbid(forbidden_lint_groups)]`
			`\| ^^^^^^^^^^^^^^^^^^^^^`
Prevent forbid from being ignored if overriden at the same level. That is, this changes `#[forbid(foo)] #[allow(foo)]` from allowing foo to forbidding foo. 2020-06-15 18:17:35 +00:00
Show number in error message even for one error Co-authored-by: Adrian <adrian.iosdev@gmail.com> 2023-11-21 15:44:16 +00:00			`error: aborting due to 1 previous error`
Prevent forbid from being ignored if overriden at the same level. That is, this changes `#[forbid(foo)] #[allow(foo)]` from allowing foo to forbidding foo. 2020-06-15 18:17:35 +00:00