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

[Arine]

On Friday, 3 January 2020 at 01:31:26 UTC, Walter Bright wrote:
> This DIP is not about changing how trusted code is inserted. If 
> you'd like to discuss that, please start a separate thread. 
> Please keep this thread on-topic about the DIP.

If issues with @safe aren't going to be considered with this DIP, 
then I'd say this DIP should be delayed until issues with @safe 
are resolved before forcing it as the default. Don't think I can 
think of a language that is safe by default that needs to use a 
hack with a separate language feature to get desired behavior.