mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
34b9932f5c
rust/src/test/ui/error-codes/E0453.stderr

31 lines
947 B
Plaintext
Raw Normal View History

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 17:14:38 -06:00
error[E0453]: allow(non_snake_case) incompatible with previous forbid
Remove licenses
2018-12-25 09:56:47 -06:00
--> $DIR/E0453.rs:3:9
Move some E0XXX to `ui`
2018-02-07 21:35:35 -06:00
|
Update UI tests
2018-02-22 18:42:32 -06:00
LL | #![forbid(non_snake_case)]
Move some E0XXX to `ui`
2018-02-07 21:35:35 -06:00
| -------------- `forbid` level set here
Update UI tests
2018-02-24 17:01:39 -06:00
LL |
Update UI tests
2018-02-22 18:42:32 -06:00
LL | #[allow(non_snake_case)]
Move some E0XXX to `ui`
2018-02-07 21:35:35 -06:00
| ^^^^^^^^^^^^^^ overruled by previous forbid
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 17:14:38 -06:00
error[E0453]: allow(non_snake_case) incompatible with previous forbid
Update tests
2020-01-08 11:02:10 -06:00
--> $DIR/E0453.rs:3:9
|
LL | #![forbid(non_snake_case)]
| -------------- `forbid` level set here
LL |
LL | #[allow(non_snake_case)]
| ^^^^^^^^^^^^^^ overruled by previous forbid
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 17:14:38 -06:00
error[E0453]: allow(non_snake_case) incompatible with previous forbid
Update tests
2020-01-08 11:02:10 -06:00
--> $DIR/E0453.rs:3:9
|
LL | #![forbid(non_snake_case)]
| -------------- `forbid` level set here
LL |
LL | #[allow(non_snake_case)]
| ^^^^^^^^^^^^^^ overruled by previous forbid
error: aborting due to 3 previous errors
Move some E0XXX to `ui`
2018-02-07 21:35:35 -06:00
update tests
2018-03-03 08:59:40 -06:00
For more information about this error, try `rustc --explain E0453`.
Reference in New Issue Copy Permalink