https://issues.dlang.org/show_bug.cgi?id=24479
Jonathan M Davis <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] | |m --- Comment #1 from Jonathan M Davis <[email protected]> --- I would point out that making deprecations errors pretty much defeats their entire purpose vs just changing the code without a deprecation. They're supposed to inform you about code that you're going to need to change without immediately breaking your code. So, anyone compiling their code with -de is going to be getting errors when they're not supposed to - and it _will_ cause problems in some cases with generic code, because template constraints routinely test whether a particular piece of code compiles or not. Of course, regardless of how deprecations are treated, there then needs to be a way to transform your code appropriately so that it no longer triggers the deprecation, but deprecations are only treated as errors if you choose to do so, and it's usually a bad idea to do so. --
