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

[Walter Bright]

On 1/2/2020 6:42 PM, 12345swordy wrote:
> What about bugs for @safe that require an DIP to fix then? Your dip doesn't 
> address this at all.

Because this DIP is about making @safe the default, not changing the behavior of 
@safe.

> Your strategy seems to make it safe by default and not 
> worry about any code that may be broken from using unsafe language features that 
> can not be simply fix with a pull request. I don't see how this is in any way 
> off-topic here. Is your current workaround for this is to abused the @trusted 
> feature?

I don't really understand what the problem is. Making code @safe by default will 
not cause code to regress into bugginess. What it will do is necessitate 
labeling code with @system that were always @system already.