> This is definitely a problem, although I'm not sure how it could be solved cleanly and efficiently.
By defining classes of warnings.
You're not using the network? You need a setting that dykes out all the network-related warnings.
Same for the database related warnings and so on.
Come on. This is nothing new. Turbo Pascal had it in the '80s.
For example, Android gets all hot and bothered about using network functions in the GUI thread (for obvious reasons) - but if I don't care my shitty garage door app freezes for a second while it's connecting to my Raspberry Pi, then I can set a pragma to disable that.