On Thu, 10 Apr 2014 13:35:34 -0400, Tommi <[email protected]> wrote:
A compiler flag is a blunt instrument. It affects all code the compiler
touches, which may or may not affect code that you are intending to
change.
Yes, such a compiler flag is a blunt and dangerous instrument and
everybody should stay away from it. But everybody agrees on those points
already. That's _not_ what you need to prove to show that such a flag
shouldn't exist. What you need to show is that no-one will ever find
them-self in a situation where such a blunt instrument would be useful.
I contend that they won't. @trusted exists and should be used for that
purpose.
Note that I could find useful disabling of const checks, or override
checks, or dynamic casts. It doesn't mean I should get a compiler switch.
-Steve
