mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
6b6cc5d576
rust/tests/ui/similar_names.stderr

88 lines
1.9 KiB
Plaintext
Raw Normal View History

UI test cleanup: Extract similar_names tests
2019-02-10 02:44:49 -06:00
error: binding's name is too similar to existing binding
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-20 22:23:22 -05:00
--> $DIR/similar_names.rs:20:9
UI test cleanup: Extract similar_names tests
2019-02-10 02:44:49 -06:00
|
LL | let bpple: i32;
| ^^^^^
|
= note: `-D clippy::similar-names` implied by `-D warnings`
note: existing binding defined here
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-20 22:23:22 -05:00
--> $DIR/similar_names.rs:18:9
UI test cleanup: Extract similar_names tests
2019-02-10 02:44:49 -06:00
|
LL | let apple: i32;
| ^^^^^
error: binding's name is too similar to existing binding
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-20 22:23:22 -05:00
--> $DIR/similar_names.rs:22:9
UI test cleanup: Extract similar_names tests
2019-02-10 02:44:49 -06:00
|
LL | let cpple: i32;
| ^^^^^
|
note: existing binding defined here
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-20 22:23:22 -05:00
--> $DIR/similar_names.rs:18:9
UI test cleanup: Extract similar_names tests
2019-02-10 02:44:49 -06:00
|
LL | let apple: i32;
| ^^^^^
error: binding's name is too similar to existing binding
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-20 22:23:22 -05:00
--> $DIR/similar_names.rs:46:9
UI test cleanup: Extract similar_names tests
2019-02-10 02:44:49 -06:00
|
LL | let bluby: i32;
| ^^^^^
|
note: existing binding defined here
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-20 22:23:22 -05:00
--> $DIR/similar_names.rs:45:9
UI test cleanup: Extract similar_names tests
2019-02-10 02:44:49 -06:00
|
LL | let blubx: i32;
| ^^^^^
error: binding's name is too similar to existing binding
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-20 22:23:22 -05:00
--> $DIR/similar_names.rs:50:9
UI test cleanup: Extract similar_names tests
2019-02-10 02:44:49 -06:00
|
LL | let coke: i32;
| ^^^^
|
note: existing binding defined here
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-20 22:23:22 -05:00
--> $DIR/similar_names.rs:48:9
UI test cleanup: Extract similar_names tests
2019-02-10 02:44:49 -06:00
|
LL | let cake: i32;
| ^^^^
error: binding's name is too similar to existing binding
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-20 22:23:22 -05:00
--> $DIR/similar_names.rs:68:9
UI test cleanup: Extract similar_names tests
2019-02-10 02:44:49 -06:00
|
LL | let xyzeabc: i32;
| ^^^^^^^
|
note: existing binding defined here
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-20 22:23:22 -05:00
--> $DIR/similar_names.rs:66:9
UI test cleanup: Extract similar_names tests
2019-02-10 02:44:49 -06:00
|
LL | let xyz1abc: i32;
| ^^^^^^^
error: binding's name is too similar to existing binding
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-20 22:23:22 -05:00
--> $DIR/similar_names.rs:72:9
UI test cleanup: Extract similar_names tests
2019-02-10 02:44:49 -06:00
|
LL | let parsee: i32;
| ^^^^^^
|
note: existing binding defined here
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-20 22:23:22 -05:00
--> $DIR/similar_names.rs:70:9
UI test cleanup: Extract similar_names tests
2019-02-10 02:44:49 -06:00
|
LL | let parser: i32;
| ^^^^^^
error: binding's name is too similar to existing binding
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-20 22:23:22 -05:00
--> $DIR/similar_names.rs:93:16
UI test cleanup: Extract similar_names tests
2019-02-10 02:44:49 -06:00
|
LL | bpple: sprang,
| ^^^^^^
|
note: existing binding defined here
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-20 22:23:22 -05:00
--> $DIR/similar_names.rs:92:16
UI test cleanup: Extract similar_names tests
2019-02-10 02:44:49 -06:00
|
LL | apple: spring,
| ^^^^^^
error: aborting due to 7 previous errors
Reference in New Issue Copy Permalink