Typical security issues in C++: why the GC isn't your enemy

[Basile B.]

On Monday, 12 December 2022 at 11:21:29 UTC, Basile B. wrote:
> On Monday, 12 December 2022 at 06:13:20 UTC, youSureAboutThat 
> wrote:
>> [...]
>
> You're supposed to catch this bug during development and with 
> your tests but here the real problem is "-release" (that 
> problem's been mentioned earlier).
>
> That switch is not well designed. Bound checks could have their 
> own front-end optimizations so we could have
>
>     -boundscheck={on|optimized|off}
>
> instead of the current system, tied to the language safety 
> system.

to extend the idea. The problem would be then that there's no way 
to disable assertions, so we also need

     -assertion={on|off}

And then we can drop -release. Actually release is more like a 
set of switches that's not always ideal. It would be better to 
have the oppostunity to control each single particular code 
instrumentation.