rust/tests/ui/double_neg.stderr

error: `--x` could be misinterpreted as pre-decrement by C programmers, is usually a no-op
  --> $DIR/double_neg.rs:7:5
   |
LL |     --x;
   |     ^^^
   |
   = note: `-D clippy::double-neg` implied by `-D warnings`
   = help: to override `-D warnings` add `#[allow(clippy::double_neg)]`

error: aborting due to previous error
Make most tests an `example` so we can run them one by one 2017-05-17 14:19:44 +02:00			error: `--x` could be misinterpreted as pre-decrement by C programmers, is usually a no-op
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 23:23:22 -04:00			`--> $DIR/double_neg.rs:7:5`
Add license header to Rust files 2018-10-06 09:18:06 -07:00			`\|`
Update *.stderr files 2018-12-27 16:57:55 +01:00			`LL \| --x;`
Add license header to Rust files 2018-10-06 09:18:06 -07:00			`\| ^^^`
			`\|`
			= note: `-D clippy::double-neg` implied by `-D warnings`
Adjust clippy tests with new rustc help suggestion for lints 2023-08-01 14:02:21 +02:00			= help: to override `-D warnings` add `#[allow(clippy::double_neg)]`
Make most tests an `example` so we can run them one by one 2017-05-17 14:19:44 +02:00
Update changed ui tests 2018-01-16 17:06:27 +01:00			`error: aborting due to previous error`