News for hackers. Stuff that matters.
Re:Rust 1.100.0 by saghm on Thursday November 12, 2026 @09:33PM (#50477372)
My semi-controversial take is that the best way to use agents for Rust is to literally turn every possible lint and warning on in clippy and require that they're treated as blocking for the agent to fix before ever saying things are done. While a few of them might be overzealous and feel tedious to work around manually, there's no need to care about it being tedious for an agent!
Re:Rust 1.100.0 by skavi on Friday November 13, 2026 @02:59AM (#50479903)
clippy lints are not universally good to follow. and with the pedantic set enabled, you quickly have bad clippy advice forcing a bunch of ugly expects in your code.

the default set plus a selection of whatever you like from the rest works better.

Re:Rust 1.100.0 by saghm on Friday November 13, 2026 @01:20PM (#50487549)
I was pretty explicitly talking about LLM-generated code. At the end of the day, you're either reviewing the code it outputs or you're not. If you are, I'd argue that you're going to be getting a bunch of ugly things in your code that you're going to want to clean up anyhow, and the tradeoff of having everything enabled is well worth it compared to what an LLM will generate with more relaxed lints. If you're not, I don't think you particularly need to care about "ugly" code.
Re:Rust 1.100.0 by derefr on Saturday November 14, 2026 @01:38PM (#50499543)
Yeah, but the point about boxing large variants still stands. That's not about aesthetics/readability, that's about micro-perf (e.g. cache-coherence), and potentially safety / atomicity. (And it can even be about compatibility, if you're doing it across an ABI boundary.)