"AIUI, or at least, from what I remember, rustfmt does this because they wanted a deterministic format that didn't depend on the style of the original code."
Well they nailed it didn't they. Repeat. Deterministic.
Like most things in coding, life and family... my personal tastes are not all that important when it comes time to publish (or have a pleasant meal.)
Being predictable and normative certainly is. Works in dating too. It's a brain thing. Formatting should logically be standardized and easily transformed is desired.
Clearly some collaboration to create CLIPPY configuration sets would tie directly to alternative standards and styles and highlight problem areas. Provided anyone cares about Dev Ops and such it could have benifit.
I have done many bizarre explorations related to natural language code, obfuscation and compaction yet am happy to CLIPPY / format comply within reason. Lol. I am a nice guy that way.
Determinism yes. Narcism no. I vote for a community defined default CLIPPY setting. If I ever voted anyway. I find voting offensive... ... ...
I have zero usage of this. Don't you just open the editor (VSC?) and apply your formatting presets?
I found the few useless warnings in VS to be useless within a design feature and might occur dozens of times.
However a contextually valid one might be buried in the pack.
Regarding the (dev cyclical?) warning review you did? That certainly should be or is a best practice. It is in RAD anyway. (Agile, whatever you use really. When isn't code review a best practice?)
To various degrees the alternatives seem either picky, elitist, unreasonable or unwise.
So... I have to ask... which are the worst, MOST annoying lints? Chuckle. Is there a top ten? Regards, Dave H.