mirror of
https://github.com/rust-lang/rust.git
synced 2024-12-04 20:54:13 +00:00
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.
53 lines
1.5 KiB
Plaintext
53 lines
1.5 KiB
Plaintext
error: this looks like you are trying to use `.. -= ..`, but you really are doing `.. = (- ..)`
|
|
--> $DIR/formatting.rs:16:6
|
|
|
|
|
LL | a =- 35;
|
|
| ^^^^
|
|
|
|
|
= note: `-D clippy::suspicious-assignment-formatting` implied by `-D warnings`
|
|
= note: to remove this lint, use either `-=` or `= -`
|
|
|
|
error: this looks like you are trying to use `.. *= ..`, but you really are doing `.. = (* ..)`
|
|
--> $DIR/formatting.rs:17:6
|
|
|
|
|
LL | a =* &191;
|
|
| ^^^^
|
|
|
|
|
= note: to remove this lint, use either `*=` or `= *`
|
|
|
|
error: this looks like you are trying to use `.. != ..`, but you really are doing `.. = (! ..)`
|
|
--> $DIR/formatting.rs:20:6
|
|
|
|
|
LL | b =! false;
|
|
| ^^^^
|
|
|
|
|
= note: to remove this lint, use either `!=` or `= !`
|
|
|
|
error: possibly missing a comma here
|
|
--> $DIR/formatting.rs:29:19
|
|
|
|
|
LL | -1, -2, -3 // <= no comma here
|
|
| ^
|
|
|
|
|
= note: `-D clippy::possible-missing-comma` implied by `-D warnings`
|
|
= note: to remove this lint, add a comma or write the expr in a single line
|
|
|
|
error: possibly missing a comma here
|
|
--> $DIR/formatting.rs:33:19
|
|
|
|
|
LL | -1, -2, -3 // <= no comma here
|
|
| ^
|
|
|
|
|
= note: to remove this lint, add a comma or write the expr in a single line
|
|
|
|
error: possibly missing a comma here
|
|
--> $DIR/formatting.rs:70:11
|
|
|
|
|
LL | -1
|
|
| ^
|
|
|
|
|
= note: to remove this lint, add a comma or write the expr in a single line
|
|
|
|
error: aborting due to 6 previous errors
|
|
|