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

[Brad Anderson]

On Tuesday, 8 April 2014 at 21:01:26 UTC, Martin Krejcirik wrote:
> 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

Asked Andrei in IRC about it and he liked -boundscheck=.

https://d.puremagic.com/issues/show_bug.cgi?id=12550

I'll try to make a pull request if someone else doesn't beat me 
to it.