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

[Steven Schveighoffer]

On 1/8/20 9:14 PM, Steven Schveighoffer wrote:
> 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.
> 
> A consideration I didn't think of before. What happens here?
> 
> extern(C) void free(void *ptr);
> 
> Is this considered safe now by default? We should not have that be the 
> case.

extern(C++) prototypes also. Basically, any function where `@safe` does 
not factor into the function mangled name, and no implementation is 
present should be assumed to be system.

-Steve