Clippy (Rust linter)

“With eager clippy and cargo lints and software design as close to the type system as possible”

“I can ask the agent to make both the compiler and clippy::pedantic happy. That gives a lot of good feedback”

“Having countless very restrictive guard rails like deny(clippy::float_arithmetic) for your usecases codifies intent about project structure”

“It's a category of lints, but some of them have much more value than others”

“Clippy has lints for panicking language operations/basic std functions”

“Static linting in Rust via clippy also makes it pretty straightforward to begin enforcing things”

“the same could be told about clippy versus improving Rust”

“found that to drastically improve the quality of the code as the LLM now should pass all clippy checks”

“telling it that it has to run clippy as well as tests before it can claim it's finished helped a decent amount”

“Clippy and fmt alone often cause the LLM to hit a snag and realize it's mistake”

“I made myself pre commit hooks for running clippy nightly and deploying my standard lints”

“you can add the undocumented_unsafe_comment lint in Clippy so that you'll never forget to document an unsafe block”

“I was able to modernize a fairly old project in literal 15 minutes by using Cargo Clippy's fix mode”

“it doesn't actually have any knowledge of how frequently each variant is actually used”

“rustc and clippy do a great job of explaining like 90% of errors”

“Those warnings and clippy lints are there to improve the quality of the code and to find bugs.”

“if Cloudflare had run the standard Clippy linter on their Rust code, and taken the results seriously, it would have prevented the issue”

“I learned about a lot of small new features that make the code cleaner through clippy.”

“"cargo clippy --fix" for Rust, essentially integrated with its linter. It doesn't fix all lints, however.”

“I would strongly recommend turning on most of clippy's lints if you want to learn rust.”

“people generally find almost all of the lints in Clippy's default set useful”

“Clippy + Rusts type system would basically ensure my software was working as close as possible to my spec before the first run.”

“just "clippy" became a movement which amassed atleast millions”

“cargo clippy can fix many constructs into cleaner versions”

“Thankfully clippy lints do exist here to help if you integrate that tooling”

“Add a single line to a single file and you get that enforced.”

“cargo clippy —-fix will automatically apply linter fixes or warning fixes when it can.”

“Never thought about it, but I'll be adding this to my standard list of deny lints now.”

“the APIs that gave rise to Clippy, Rover, and (regrettably) even Bonzi Buddy”

“The solution in both languages is to use a linter to warn about the use of partial functions”

“Clippy (and the Rust compiler proper) can provide so much of the concrete iterative feedback an agent needs”

“I don't need clippy for the right to repair movement though.”

“the only thing Clippy was missing for it to be genuinely useful was... LLMs”

“the most useless dumbest biggest failure of a mega corporation”

“it wasn't as bad as it could be because the technology just wasn't there to begin with”

“you can forbid slice access and direct unwraps with clippy”

“Put that in your CI pipeline, and voila. Global crash averted.”

“things like "cargo clippy" which tell you how you could improve your code”

“This should be the default for production code at companies like Cloudflare.”

“clippy / rustc has very good diagnostics and usually tells you "do X to fix this"”