How DMD's -w *Prevents* Me From Seeing My Warnings

[Don]

Nick Sabalausky wrote:
> Real-world example that's actually happened to me far too many times (and 
> has *never* happened to me in any language other than D):
> 
> I'm writing app A and library B, both of which depend on an external library 
> C. I compile A/B with -w to check for any warnings in my code. Either it has 
> warnings and I fix them or it just simply passes.
> 
> Then, I make a change to A/B that brings in previously unused code from C 
> (or I just simply update C), and this new code in C just happens to have 
> something that triggers a warning (you can say "C should never release 
> without fixing all warnings first" all you want, but the fact is: it still 
> happens).

The idea of "optional errors" is nonsense. Especially for library 
developers, they are NOT optional.