rust/tests/ui/author.rs

//@ check-pass

fn main() {
    #[clippy::author]
    let x: char = 0x45 as char;
}
Merge commit '9f9a822509e5ad3e560cbbe830d1013f936fca28' into clippy-subtree-update 2025-02-28 23:20:48 +01:00			`//@ check-pass`

Fix author lint The author lint was generating invalid code as shown on issue: https://github.com/rust-lang-nursery/rust-clippy/issues/2442 I've changed the generated code to properly track cast expressions. Unfortunatelly, I've had to rewrite the `visit_decl` method, to avoid that last if of the chain will be added. After looking at the code, this last line was being added because of the `let x: char` part, but not because of the `0x45df as char` expression. It seems that let statements should not generate code on the author lint, but I'm not sure that this is true or if I'm breaking something on other code generation parts. Finally, I've added a test for the author lint, but I'm not sure that this needs to be added to the testsuite. 2018-02-24 02:02:48 +01:00			`fn main() {`
Use the new scoped tool attributes 2018-05-19 14:04:57 +02:00			`#[clippy::author]`
Fix author lint The author lint was generating invalid code as shown on issue: https://github.com/rust-lang-nursery/rust-clippy/issues/2442 I've changed the generated code to properly track cast expressions. Unfortunatelly, I've had to rewrite the `visit_decl` method, to avoid that last if of the chain will be added. After looking at the code, this last line was being added because of the `let x: char` part, but not because of the `0x45df as char` expression. It seems that let statements should not generate code on the author lint, but I'm not sure that this is true or if I'm breaking something on other code generation parts. Finally, I've added a test for the author lint, but I'm not sure that this needs to be added to the testsuite. 2018-02-24 02:02:48 +01:00			`let x: char = 0x45 as char;`
			`}`