That is so cool! TIL! and I just made a tweak on dotty about nowarn and didn't notice.

Not that I didn't believe you, but I had to try it out on my test file.

  |            unused explicit parameter
Matching filters for @nowarn or -Wconf:
  - id=E198
  - name=UnusedSymbol

Every code base should have class dowarn extends nowarn("v").

That doesn't work yet.

Changing compiler flags is much more tedious than adding an annotation to the source and rebuilding.

Scala 3 -explain is an obvious candidate.

For Scala 2, I looked through the settings. Scoped -Vprint would cool, maybe -Vtyper too, but both are for advanced users. -Vcyclic is a global flag, I don't think an annotation would work for that.

So maybe -explain is the only real opportunity. I'll create a ticket to see if they like the idea, if they want to reuse @nowarn("v") for that, or some new annotation.

flags vs annotations is sad but true. Also counter-intuitive from an old school perspective. Modifying source is heavyweight, but because of the "build tool", flipping an option is heavier.

I don't use an IDE, although previously I used Eclipse for Java projects, but I can see the "local" use case: there is some weirdness in my code, it shows a red squiggle or perhaps amber, I want to click an icon to show what I can do to silence the squiggle.

That workflow is entirely local.

The missing piece is still an audit to tell me what warnings were modified (locally suppressed) in my code.