Enabling some runtime checks in release mode

[5nyper]

I suggest we have some options in release mode that have little impact to it's performance yet have bounds checking and null dereferencing checks on by default. The reason being is that currently, the '-d:release' option disables all runtime checks, even those that have a relatively minor impact on performance. Considering the prevalence of buffer-overflow and off-by-one bugs in programs and libraries, I would like to suggest that the default configuration file be modified such that release mode doesn't turn off bounds-checking. Even if programmers perform standard testing of their programs, buffer overflow errors can still happen in unlikely scenarios and thus unlikely to be tested.

[Varriount]

Anyone against this change?

[Araq]

Yes. I am. Instead we need a proper debug/release/safety split where -d:safety enables all these fear based things.

[5nyper]

So basically instead of having it enabled in the -d:release flag we create a separate flag to enable the run-time checks in release mode?

[narimiran]

Can we close this?

[FedericoCeratto]

See nim-lang/RFCs#4