https://issues.dlang.org/show_bug.cgi?id=12550
--- Comment #8 from Steven Schveighoffer <[email protected]> --- (In reply to Martin Krejcirik from comment #7) > (In reply to Steven Schveighoffer from comment #6) > > The developer is not always the builder. e.g. template code. > > Also the builder is not always the developer. It's much easier (and I would > say safer), changing a command line option, than changing the code, just to > test how fast it runs. And incorrect. If you are trying to fix a performance issue, removing bounds checks on an entire program is much more damaging and fruitless than removing bounds checks on a bottleneck loop that you have read and understood. I find the argument unconvincing that someone who is working on performance is simply going to do this as a test measure before doing their *real* profiling task. We should do as much as possible to avoid blunt-instrument speedups that compromise the safety of systems that are *specifically* labelled safe without any care or thought. Focused optimization via profiling is a better approach in every case. --
