How do I temporarily show Clippy warnings?

[vi]

I know that I can edit settings to invoke cargo clippy instead of cargo check, save a file to trigger RA recheck, observe and fix Clippy issues in the project, then change settings back to use usual cargo check.

Is there (or should there be) a better, more user-friendly way of viewing Clippy diagnostics without modifying settings every time, also without opting in to Clippy notices permanently?

[jonas-schievink]

I've added a cargo clippy task preset in #12326. Unfortunately that doesn't use the same diagnostics rendering logic as Check-on-Save does, so the result will be lower-quality diagnostics, but it's a start.

[flodiebold]

IIRC there were some discussions (maybe even a PR) about adding a check-on-command, and it was rejected because task presets can be used instead. I think the diagnostic rendering (including quick fixes, potentially deduplication between the check and our own diagnostics, etc.), and the fact that task presets are VSCode specific, are arguments to build this into rust-analyzer properly though.

[Jesse-Bakker]

Since version 3.17, LSP has support for pull-based diagnostic reporting. There is no built-in way to specify which diagnostics to report unfortunately, so it might need an extension to allow for that.