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.
21 lines
427 B
Rust
21 lines
427 B
Rust
// non rustfixable, see redundant_closure_call_fixable.rs
|
|
|
|
#![warn(clippy::redundant_closure_call)]
|
|
|
|
fn main() {
|
|
let mut i = 1;
|
|
|
|
// lint here
|
|
let mut k = (|m| m + 1)(i);
|
|
|
|
// lint here
|
|
k = (|a, b| a * b)(1, 5);
|
|
|
|
// don't lint these
|
|
#[allow(clippy::needless_return)]
|
|
(|| return 2)();
|
|
(|| -> Option<i32> { None? })();
|
|
#[allow(clippy::try_err)]
|
|
(|| -> Result<i32, i32> { Err(2)? })();
|
|
}
|