ac9dd36856
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.
52 lines
1.4 KiB
Plaintext
52 lines
1.4 KiB
Plaintext
error: 5 bindings with single-character names in scope
|
|
--> $DIR/many_single_char_names.rs:5:9
|
|
|
|
|
LL | let a: i32;
|
|
| ^
|
|
LL | let (b, c, d): (i32, i64, i16);
|
|
| ^ ^ ^
|
|
...
|
|
LL | let e: i32;
|
|
| ^
|
|
|
|
|
= note: `-D clippy::many-single-char-names` implied by `-D warnings`
|
|
|
|
error: 6 bindings with single-character names in scope
|
|
--> $DIR/many_single_char_names.rs:5:9
|
|
|
|
|
LL | let a: i32;
|
|
| ^
|
|
LL | let (b, c, d): (i32, i64, i16);
|
|
| ^ ^ ^
|
|
...
|
|
LL | let e: i32;
|
|
| ^
|
|
LL | let f: i32;
|
|
| ^
|
|
|
|
error: 5 bindings with single-character names in scope
|
|
--> $DIR/many_single_char_names.rs:5:9
|
|
|
|
|
LL | let a: i32;
|
|
| ^
|
|
LL | let (b, c, d): (i32, i64, i16);
|
|
| ^ ^ ^
|
|
...
|
|
LL | e => panic!(),
|
|
| ^
|
|
|
|
error: 8 bindings with single-character names in scope
|
|
--> $DIR/many_single_char_names.rs:30:13
|
|
|
|
|
LL | fn bindings(a: i32, b: i32, c: i32, d: i32, e: i32, f: i32, g: i32, h: i32) {}
|
|
| ^ ^ ^ ^ ^ ^ ^ ^
|
|
|
|
error: 8 bindings with single-character names in scope
|
|
--> $DIR/many_single_char_names.rs:33:10
|
|
|
|
|
LL | let (a, b, c, d, e, f, g, h): (bool, bool, bool, bool, bool, bool, bool, bool) = unimplemented!();
|
|
| ^ ^ ^ ^ ^ ^ ^ ^
|
|
|
|
error: aborting due to 5 previous errors
|
|
|