rust-clippy/tests/ui/formatting.stderr

error: this looks like you are trying to use `.. -= ..`, but you really are doing `.. = (- ..)`
  --> $DIR/formatting.rs:16:6
   |
LL |     a =- 35;
   |      ^^^^
   |
   = note: to remove this lint, use either `-=` or `= -`
   = note: `-D clippy::suspicious-assignment-formatting` implied by `-D warnings`

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: to remove this lint, add a comma or write the expr in a single line
   = note: `-D clippy::possible-missing-comma` implied by `-D warnings`

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
test formatting: don't format tests/ui/formatting.rs 2018-12-10 14:46:01 +00:00			error: this looks like you are trying to use `.. -= ..`, but you really are doing `.. = (- ..)`
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/formatting.rs:16:6`
Update *.stderr files 2018-12-27 15:57:55 +00:00			`\|`
			`LL \| a =- 35;`
			`\| ^^^^`
			`\|`
			= note: to remove this lint, use either `-=` or `= -`
bless clippy 2022-09-22 16:04:22 +00:00			= note: `-D clippy::suspicious-assignment-formatting` implied by `-D warnings`
test formatting: don't format tests/ui/formatting.rs 2018-12-10 14:46:01 +00:00
			error: this looks like you are trying to use `.. = ..`, but you really are doing `.. = ( ..)`
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/formatting.rs:17:6`
Update *.stderr files 2018-12-27 15:57:55 +00:00			`\|`
			`LL \| a =* &191;`
			`\| ^^^^`
			`\|`
			= note: to remove this lint, use either `=` or `= `
test formatting: don't format tests/ui/formatting.rs 2018-12-10 14:46:01 +00:00
			error: this looks like you are trying to use `.. != ..`, but you really are doing `.. = (! ..)`
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/formatting.rs:20:6`
Update *.stderr files 2018-12-27 15:57:55 +00:00			`\|`
			`LL \| b =! false;`
			`\| ^^^^`
			`\|`
			= note: to remove this lint, use either `!=` or `= !`
test formatting: don't format tests/ui/formatting.rs 2018-12-10 14:46:01 +00:00
rustup and compile-fail -> ui test move 2017-02-07 20:05:30 +00:00			`error: possibly missing a comma 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-21 03:23:22 +00:00			`--> $DIR/formatting.rs:29:19`
Update *.stderr files 2018-12-27 15:57:55 +00:00			`\|`
			`LL \| -1, -2, -3 // <= no comma here`
			`\| ^`
			`\|`
			`= note: to remove this lint, add a comma or write the expr in a single line`
bless clippy 2022-09-22 16:04:22 +00:00			= note: `-D clippy::possible-missing-comma` implied by `-D warnings`
rustup and compile-fail -> ui test move 2017-02-07 20:05:30 +00:00
			`error: possibly missing a comma 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-21 03:23:22 +00:00			`--> $DIR/formatting.rs:33:19`
Update *.stderr files 2018-12-27 15:57:55 +00:00			`\|`
			`LL \| -1, -2, -3 // <= no comma here`
			`\| ^`
			`\|`
			`= note: to remove this lint, add a comma or write the expr in a single line`
rustup and compile-fail -> ui test move 2017-02-07 20:05:30 +00:00
dont fire possible_missing_comma if intendation is present 2020-01-23 21:27:01 +00:00			`error: possibly missing a comma 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-21 03:23:22 +00:00			`--> $DIR/formatting.rs:70:11`
dont fire possible_missing_comma if intendation is present 2020-01-23 21:27:01 +00:00			`\|`
			`LL \| -1`
			`\| ^`
			`\|`
			`= note: to remove this lint, add a comma or write the expr in a single line`

Merge commit '4911ab124c481430672a3833b37075e6435ec34d' into clippyup 2020-12-20 16:19:49 +00:00			`error: aborting due to 6 previous errors`
Update changed ui tests 2018-01-16 16:06:27 +00:00