mirror of
https://github.com/rust-lang/rust-clippy
synced 2024-09-21 07:01:54 +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.
73 lines
1.2 KiB
Rust
73 lines
1.2 KiB
Rust
#![warn(clippy::all)]
|
|
#![allow(unused_variables)]
|
|
#![allow(unused_assignments)]
|
|
#![allow(clippy::if_same_then_else)]
|
|
#![allow(clippy::deref_addrof)]
|
|
#![allow(clippy::nonminimal_bool)]
|
|
|
|
fn foo() -> bool {
|
|
true
|
|
}
|
|
|
|
#[rustfmt::skip]
|
|
fn main() {
|
|
// weird op_eq formatting:
|
|
let mut a = 42;
|
|
a =- 35;
|
|
a =* &191;
|
|
|
|
let mut b = true;
|
|
b =! false;
|
|
|
|
// those are ok:
|
|
a = -35;
|
|
a = *&191;
|
|
b = !false;
|
|
|
|
// possible missing comma in an array
|
|
let _ = &[
|
|
-1, -2, -3 // <= no comma here
|
|
-4, -5, -6
|
|
];
|
|
let _ = &[
|
|
-1, -2, -3 // <= no comma here
|
|
*4, -5, -6
|
|
];
|
|
|
|
// those are ok:
|
|
let _ = &[
|
|
-1, -2, -3,
|
|
-4, -5, -6
|
|
];
|
|
let _ = &[
|
|
-1, -2, -3,
|
|
-4, -5, -6,
|
|
];
|
|
let _ = &[
|
|
1 + 2, 3 +
|
|
4, 5 + 6,
|
|
];
|
|
|
|
// don't lint for bin op without unary equiv
|
|
// issue 3244
|
|
vec![
|
|
1
|
|
/ 2,
|
|
];
|
|
// issue 3396
|
|
vec![
|
|
true
|
|
| false,
|
|
];
|
|
|
|
// don't lint if the indentation suggests not to
|
|
let _ = &[
|
|
1 + 2, 3
|
|
- 4, 5
|
|
];
|
|
// lint if it doesn't
|
|
let _ = &[
|
|
-1
|
|
-4,
|
|
];
|
|
}
|