News for hackers. Stuff that matters.
Re:Compiler Errors for Humans (2015) by jamesmunns on Thursday November 24, 2022 @12:14PM (#33733702)
Both Rust (via 'cargo fix') and Clang (via `clang-tidy -fix` have ways of doing this, I don't think I've seen someone offer this automatically/interactively though.

I don't think I've ever used them, but I've ABSOLUTELY used suggested fixes from LSP/rust-analyzer tools, which fit much more into my typical workflow. For things like match statements in Rust (which need to be exhaustive), I now have muscle memory to just write an empty match statement, and trigger the first LSP/r-a suggestion, which fills the match block with placeholder items.

I guess I see LSP as my "compiler in interactive mode" interface (even if that isn't EXACTLY true).

There are no comments on this comment yet.