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

[JN]

On Thursday, 2 January 2020 at 17:06:44 UTC, Guillaume Piolat 
wrote:
> - I don't think D defaults are wrong, they let you write code 
> that is as-crappy-as-needed and gets better later.
>

Personally, I don't care for memory safety either, I don't write 
any critical software or anything like that so crashes are not 
much of a concern for me. But I think there is value in forcing 
safe defaults. With languages like C# or Rust, which are safe by 
default and allow unsafe sections, when you encounter a crash, 
usually all you have to do is just go over the unsafe sections 
(which should be rare and limited in size) to find the culprit.

I don't believe in "write crappy as needed and get better later" 
methodology, because that later usually never happens. And if you 
didn't write the safe code from the start, it's much harder to 
convert a codebase. Meanwhile, if you're writing it safe from the 
scratch, it's much easier as long as you follow some rules.