Feedback Thread: DIP 1028--Make @safe the Default--Final Review

[Stefan Koch]

On Wednesday, 25 March 2020 at 08:37:53 UTC, Walter Bright wrote:
> On 3/25/2020 12:29 AM, ag0aep6g wrote:
>> The DIP says about `extern` functions:
>> 
>>> An unmarked extern (D) function will now be considered @safe.
>> 
>> It does not say clearly what happens with other `extern` 
>> functions.
>> 
>> For unmarked `extern (C)` and `extern (C++)` functions, the 
>> DIP should either say that they will still be considered 
>> @system, or it should say that they become errors.
>> 
>> The DIP should also mention `extern (Windows)` and `extern 
>> (Objective-C)`, or just have a catch-all sentence about "other 
>> `extern` functions".
>
> Since @safe will now be the default, all extern functions will 
> be @safe. It shouldn't be necessary to enumerate what 
> declarations are covered by this. It would only be necessary to 
> enumerate declarations which would not be.

Are you talking about the case where an extern(C) function is 
defined in D code?