nordic-dev.net/rust
nordic-dev.net/rust
2
0
Fork 0
mirror of https://github.com/rust-lang/rust.git synced 2025-02-26 05:44:26 +00:00
Code Issues Packages Projects Releases Wiki Activity
eef02c453f
rust/tests/ui/lint/crate_level_only_lint.stderr

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

75 lines
2.4 KiB
Plaintext
Raw Normal View History

Implement crate level only lints checking.
2020-06-13 01:58:24 +00:00
error: allow(uncommon_codepoints) is ignored unless specified at crate level
--> $DIR/crate_level_only_lint.rs:4:10
|
LL | #![allow(uncommon_codepoints)]
| ^^^^^^^^^^^^^^^^^^^
|
note: the lint level is defined here
--> $DIR/crate_level_only_lint.rs:1:30
|
LL | #![deny(uncommon_codepoints, unused_attributes)]
| ^^^^^^^^^^^^^^^^^
error: allow(uncommon_codepoints) is ignored unless specified at crate level
Don't abort compilation after giving a lint error The only reason to use `abort_if_errors` is when the program is so broken that either: 1. later passes get confused and ICE 2. any diagnostics from later passes would be noise This is never the case for lints, because the compiler has to be able to deal with `allow`-ed lints. So it can continue to lint and compile even if there are lint errors.
2021-07-21 03:23:22 +00:00
--> $DIR/crate_level_only_lint.rs:9:9
Implement crate level only lints checking.
2020-06-13 01:58:24 +00:00
|
LL | #[allow(uncommon_codepoints)]
| ^^^^^^^^^^^^^^^^^^^
error: allow(uncommon_codepoints) is ignored unless specified at crate level
Don't abort compilation after giving a lint error The only reason to use `abort_if_errors` is when the program is so broken that either: 1. later passes get confused and ICE 2. any diagnostics from later passes would be noise This is never the case for lints, because the compiler has to be able to deal with `allow`-ed lints. So it can continue to lint and compile even if there are lint errors.
2021-07-21 03:23:22 +00:00
--> $DIR/crate_level_only_lint.rs:17:9
Implement crate level only lints checking.
2020-06-13 01:58:24 +00:00
|
LL | #[allow(uncommon_codepoints)]
| ^^^^^^^^^^^^^^^^^^^
error: allow(uncommon_codepoints) is ignored unless specified at crate level
--> $DIR/crate_level_only_lint.rs:4:10
|
LL | #![allow(uncommon_codepoints)]
| ^^^^^^^^^^^^^^^^^^^
Add a note to duplicate diagnostics
2023-10-04 18:34:50 +00:00
|
= note: duplicate diagnostic emitted due to `-Z deduplicate-diagnostics=no`
Implement crate level only lints checking.
2020-06-13 01:58:24 +00:00
error: allow(uncommon_codepoints) is ignored unless specified at crate level
Don't abort compilation after giving a lint error The only reason to use `abort_if_errors` is when the program is so broken that either: 1. later passes get confused and ICE 2. any diagnostics from later passes would be noise This is never the case for lints, because the compiler has to be able to deal with `allow`-ed lints. So it can continue to lint and compile even if there are lint errors.
2021-07-21 03:23:22 +00:00
--> $DIR/crate_level_only_lint.rs:9:9
Implement crate level only lints checking.
2020-06-13 01:58:24 +00:00
|
LL | #[allow(uncommon_codepoints)]
| ^^^^^^^^^^^^^^^^^^^
Add a note to duplicate diagnostics
2023-10-04 18:34:50 +00:00
|
= note: duplicate diagnostic emitted due to `-Z deduplicate-diagnostics=no`
Implement crate level only lints checking.
2020-06-13 01:58:24 +00:00
error: allow(uncommon_codepoints) is ignored unless specified at crate level
Don't abort compilation after giving a lint error The only reason to use `abort_if_errors` is when the program is so broken that either: 1. later passes get confused and ICE 2. any diagnostics from later passes would be noise This is never the case for lints, because the compiler has to be able to deal with `allow`-ed lints. So it can continue to lint and compile even if there are lint errors.
2021-07-21 03:23:22 +00:00
--> $DIR/crate_level_only_lint.rs:17:9
Implement crate level only lints checking.
2020-06-13 01:58:24 +00:00
|
LL | #[allow(uncommon_codepoints)]
| ^^^^^^^^^^^^^^^^^^^
Add a note to duplicate diagnostics
2023-10-04 18:34:50 +00:00
|
= note: duplicate diagnostic emitted due to `-Z deduplicate-diagnostics=no`
Implement crate level only lints checking.
2020-06-13 01:58:24 +00:00
Don't abort compilation after giving a lint error The only reason to use `abort_if_errors` is when the program is so broken that either: 1. later passes get confused and ICE 2. any diagnostics from later passes would be noise This is never the case for lints, because the compiler has to be able to deal with `allow`-ed lints. So it can continue to lint and compile even if there are lint errors.
2021-07-21 03:23:22 +00:00
error: allow(uncommon_codepoints) is ignored unless specified at crate level
--> $DIR/crate_level_only_lint.rs:4:10
|
LL | #![allow(uncommon_codepoints)]
| ^^^^^^^^^^^^^^^^^^^
Add a note to duplicate diagnostics
2023-10-04 18:34:50 +00:00
|
= note: duplicate diagnostic emitted due to `-Z deduplicate-diagnostics=no`
Don't abort compilation after giving a lint error The only reason to use `abort_if_errors` is when the program is so broken that either: 1. later passes get confused and ICE 2. any diagnostics from later passes would be noise This is never the case for lints, because the compiler has to be able to deal with `allow`-ed lints. So it can continue to lint and compile even if there are lint errors.
2021-07-21 03:23:22 +00:00
error: allow(uncommon_codepoints) is ignored unless specified at crate level
--> $DIR/crate_level_only_lint.rs:9:9
|
LL | #[allow(uncommon_codepoints)]
| ^^^^^^^^^^^^^^^^^^^
Add a note to duplicate diagnostics
2023-10-04 18:34:50 +00:00
|
= note: duplicate diagnostic emitted due to `-Z deduplicate-diagnostics=no`
Don't abort compilation after giving a lint error The only reason to use `abort_if_errors` is when the program is so broken that either: 1. later passes get confused and ICE 2. any diagnostics from later passes would be noise This is never the case for lints, because the compiler has to be able to deal with `allow`-ed lints. So it can continue to lint and compile even if there are lint errors.
2021-07-21 03:23:22 +00:00
error: allow(uncommon_codepoints) is ignored unless specified at crate level
--> $DIR/crate_level_only_lint.rs:17:9
|
LL | #[allow(uncommon_codepoints)]
| ^^^^^^^^^^^^^^^^^^^
Add a note to duplicate diagnostics
2023-10-04 18:34:50 +00:00
|
= note: duplicate diagnostic emitted due to `-Z deduplicate-diagnostics=no`
Don't abort compilation after giving a lint error The only reason to use `abort_if_errors` is when the program is so broken that either: 1. later passes get confused and ICE 2. any diagnostics from later passes would be noise This is never the case for lints, because the compiler has to be able to deal with `allow`-ed lints. So it can continue to lint and compile even if there are lint errors.
2021-07-21 03:23:22 +00:00
error: aborting due to 9 previous errors
Implement crate level only lints checking.
2020-06-13 01:58:24 +00:00
Reference in New Issue Copy Permalink