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

Tue Apr 8 14:01:25 PDT 2014

On Tuesday, 8 April 2014 at 20:20:59 UTC, Brad Anderson wrote:
> Good point. I think perhaps a -boundscheck is in order if the

What about:

-boundscheck=<none|safe|all>

which defaults to 'all' and to 'safe' in combination with -release

-noboundscheck would be the same as -boundscheck=none

If compatibility is not an issue and we want to keep it simple, 
than -release should just turn off asserts and contracts.