DIP 1028---Make @safe the Default---Community Review Round 1

Fri Jan 3 22:23:41 UTC 2020

On Friday, 3 January 2020 at 22:13:28 UTC, Steven Schveighoffer 
wrote:
>
> I'd probably have to adjust a few things, and then it will 
> build. The benefit is huge, because then someone doesn't have 
> to choose between memory safety and iopipe speed. If the 
> compiler complained about this when I was developing it, I'd 
> fix the problems as they happened.
>

Can anyone produce ONE example of a memory corruption code they 
write that was found with use of marking something @safe?