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

Arine arine123445128843 at gmail.com
Thu Jan 9 19:20:51 UTC 2020

On Thursday, 9 January 2020 at 19:00:27 UTC, Steven Schveighoffer 
> But I think this is digressing from the DIP discussion quite a 
> bit. Probably best to continue if necessary in a new thread.
> -Steve

I don't agree. This is discussing a method to implement safe be 
default. If you are going to make a breaking change that causes 
almost all code to not compile, all tutorials and documentation 
to be invalidated. Every existing discussion to become obsolete. 
It makes sense to view all options. D's proposed safe by default 
is sub-par to comparison to Rust's and C#'s safe by default that 
use one keyword and unsafe blocks. Even though it lists Rust and 
C# as part of the reason for this change, it doesn't go into 
detail about how D's implementation is fundamentally different 
from how C# and Rust implement safe by default. You can't "turn 
on" safety, you can only turn it off with a keyword.

More information about the Digitalmars-d mailing list