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

Steven Schveighoffer schveiguy at gmail.com
Fri Jan 3 15:23:10 UTC 2020

On 1/2/20 4:47 AM, Mike Parker wrote:
> This is the feedback thread for the first round of Community Review for 
> DIP 1028, "Make @safe the Default":
> https://github.com/dlang/DIPs/blob/1b705f8d4faa095d6d9e3a1b81d6cfa6d688554b/DIPs/DIP1028.md 
> All review-related feedback on and discussion of the DIP should occur in 
> this thread. The review period will end at 11:59 PM ET on January 16, or 
> when I make a post declaring it complete.
> At the end of Round 1, if further review is deemed necessary, the DIP 
> will be scheduled for another round of Community Review. Otherwise, it 
> will be queued for the Final Review and Formal Assessment.
> Anyone intending to post feedback in this thread is expected to be 
> familiar with the reviewer guidelines:
> https://github.com/dlang/DIPs/blob/master/docs/guidelines-reviewers.md
> *Please stay on topic!*
> Thanks in advance to all who participate.

Some sticky points:

1. Currenty the compiler can "give up" on attribute inference, and 
therefore leaves functions as @system. What happens when @safe is the 
default? I would recommend that they should be inferred @safe, but this 
might be a code-breaking in some cases.

2. I'll echo here what other have said, because it's REALLY important: 
do NOT recommend slapping @trusted on anything. It's a very very bad 
idea, and destroys the whole concept of @safe. Rather, put @system on 
functions that have to be @system.


More information about the Digitalmars-d mailing list