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.
66 lines
1.0 KiB
Rust
66 lines
1.0 KiB
Rust
// run-rustfix
|
|
#![warn(clippy::deref_addrof)]
|
|
|
|
fn get_number() -> usize {
|
|
10
|
|
}
|
|
|
|
fn get_reference(n: &usize) -> &usize {
|
|
n
|
|
}
|
|
|
|
#[allow(clippy::double_parens)]
|
|
#[allow(unused_variables, unused_parens)]
|
|
fn main() {
|
|
let a = 10;
|
|
let aref = &a;
|
|
|
|
let b = a;
|
|
|
|
let b = get_number();
|
|
|
|
let b = *get_reference(&a);
|
|
|
|
let bytes: Vec<usize> = vec![1, 2, 3, 4];
|
|
let b = bytes[1..2][0];
|
|
|
|
//This produces a suggestion of 'let b = (a);' which
|
|
//will trigger the 'unused_parens' lint
|
|
let b = (a);
|
|
|
|
let b = a;
|
|
|
|
#[rustfmt::skip]
|
|
let b = a;
|
|
|
|
let b = &a;
|
|
|
|
let b = *aref;
|
|
}
|
|
|
|
#[rustfmt::skip]
|
|
macro_rules! m {
|
|
($visitor: expr) => {
|
|
$visitor
|
|
};
|
|
}
|
|
|
|
#[rustfmt::skip]
|
|
macro_rules! m_mut {
|
|
($visitor: expr) => {
|
|
$visitor
|
|
};
|
|
}
|
|
|
|
#[derive(Copy, Clone)]
|
|
pub struct S;
|
|
impl S {
|
|
pub fn f(&self) -> &Self {
|
|
m!(self)
|
|
}
|
|
#[allow(unused_mut)] // mut will be unused, once the macro is fixed
|
|
pub fn f_mut(mut self) -> Self {
|
|
m_mut!(self)
|
|
}
|
|
}
|