A serious security bug... caused by no bounds checking.

[Tommi]

On Thursday, 10 April 2014 at 17:56:04 UTC, Steven Schveighoffer 
wrote:
> @safe code can be marked as @trusted instead, and nothing 
> changes, except @trusted code can have bounds checks removed. 
> How does this not work as a solution?

A compiler flag for disabling bounds checking is a blunt 
instrument. But using search & replace to change each @safe to 
@trusted is a blunt _and_ inconvenient instrument.