rust/tests/ui/double_neg.rs

#[warn(clippy::double_neg)]
#[allow(clippy::no_effect)]
fn main() {
    let x = 1;
    -x;
    -(-x);
    --x;
    //~^ ERROR: `--x` could be misinterpreted as pre-decrement by C programmers, is usuall
    //~| NOTE: `-D clippy::double-neg` implied by `-D warnings`
}
Adapt ui-tests to the tool_lints 2018-07-28 10:34:52 -05:00			`#[warn(clippy::double_neg)]`
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			`#[allow(clippy::no_effect)]`
new lint: double_neg 2016-06-29 18:00:25 -05:00			`fn main() {`
			`let x = 1;`
			`-x;`
			`-(-x);`
remove all //~ from tests 2017-02-08 07:58:07 -06:00			`--x;`
Merge commit '080b587854a73f2a8cbaecff1884860a78e2ff37' into clippyup 2023-08-24 14:32:12 -05:00			//~^ ERROR: `--x` could be misinterpreted as pre-decrement by C programmers, is usuall
			//~\| NOTE: `-D clippy::double-neg` implied by `-D warnings`
new lint: double_neg 2016-06-29 18:00:25 -05:00			`}`