https://issues.dlang.org/show_bug.cgi?id=14367
--- Comment #5 from Don <[email protected]> --- I think this bug should be closed as invalid. As stated in comment 3, warnings and deprecations are two very different things. The bug report is based on the misconception that they are the same. deprecation = this code used to be correct, but now it is an error. The code must be fixed, but it is not urgent. warning = the code might be perfectly correct. Bearophile's comment 4 is something different. It is a real issue. I think it would best be fixed by removing warnings from the compiler entirely (which is in practice what Bearophile is asking for, if they are enabled by default they are just errors). The whole idea of an "optional error" is absurd. If a single library does not compile without warnings, then the app cannot be compiled with warnings enabled either. So warnings are usable only if all libraries respect them, which means they are not optional for libraries! But that is a discussion for a different place. --
