rust-clippy

[quote="scottmcm, post:21, topic:143448"] So going back down again, if there's something worth doing here, it'd be linting … Shadowing like let x = x.parse()?; or if let Some(x) = x { is IMHO essential and as a result I'd never agree to totally remove shadowing. But also if people find good heuristics I'd be happy to have some kinds of linting about stuff. The only time I remember getting bit by shadowing was a f32 shadowed by another f32 where I was trying to use the older one. [/quote] Clippy already has a lint for this: shadow_unrelated (along with shadow_reuse and shadow_same which can be used to further restrict shadowing). However, unsurprisingly, it has false-positive cases, a couple of which I found myself: - rust-clippy#11827 - rust-clippy#14537 - rust-clippy#11423 - rust-clippy#3200 (debatable)

Clippy Changelog Cat Contest 1.100 is now open, submit your cat pics! Go submit your cat for a chance to become the next release's official winner! rust-clippy#17951

I wrote a clippy lint (rust-clippy#17129) to catch structs that are too big, but seems others think it's too strict. I still think it's a good idea.

Just got my first Rust PR merged! A fix to Clippy's double_comparisons lint. 🦀 PR link: rust-clippy#17907 #rust-lang #clippy #open-source

rust-clippy#8609 Thankfully someone is on it. Does Rust have a flag or lint to just disable recursion? I _never_ use it

two of my prs got merged into rust-clippy rust-clippy#17863 rust-clippy#17879

happy birthday clippy lint list! love how the design is still basically the same :D rust-clippy#1091

RustConf 2025 Interview: Manish Goregaokar, Rust Devtools At RustConf 2025 in Seattle, the Rust Project Content Team talks with Manish Goregaokar: Clippy co-creator, Servo alum, and around eleven years in the Rust Project, now working on internationalization with ICU4X and interop tooling with Diplomat. Manish shares how contributing to Servo in 2013-2014, when nightly Rust broke every few weeks, pulled him from working with Rust into working on Rust, and how a silly project full of lints became Clippy. Topics include: • Clippy's origins and the culture of mentorship inherited from Servo: writing lints as an accessible on-ramp to compiler internals • How the Rust community changed from one tight-knit group into many overlapping worlds, and why that's healthy • The surprise of 1.0: the flood of Python and JavaScript developers who were always interested in systems programming once the barrier came down • An ontology of interop tooling: unidirectional versus bidirectional tools, and why "other languages calling Rust libraries" was the underserved direction • Diplomat: bridge modules generating a C API, a typed AST, and independently developed backends for C, C++, JavaScript/Wasm, Dart, Kotlin, Java, and Python • ICU4X: internationalization designed from scratch to be modular, embedded-friendly, and pluggable about data, so your app doesn't mispluralize Polish • Restraint about writing crates de novo, nerd-sniping yourself, and designs like ZeroVec and Yoke that others had to convince him to build • jj (Jujutsu): a Rust version control system with changes as first-class concepts distinct from commits Links mentioned: Manish on GitHub: github.com/Manishearth Clippy: rust-lang/rust-clippy Servo: servo.org ICU4X: unicode-org/icu4x Diplomat: rust-diplomat/diplomat UniFFI: mozilla/uniffi-rs CXX: cxx.rs bindgen: rust-lang/rust-bindgen jj (Jujutsu): jj-vcs/jj Interview conducted on behalf of the Rust Project Content Team.