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

[Guillaume Piolat]

On Thursday, 2 January 2020 at 09:47:48 UTC, 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.

I'm still against:
- it break everything for everyone, so we'll lose working 
packages on code.dlang.org who happen to have no maintainer but 
have worked for years
- it doesn't seem like Community input is wanted in any way, it's 
all "there is no choice"
- ...but doing it just move the default. It's not an enabler for 
"safe reference counting" or things like that, since it's just a 
default.
- benefits are overstated since D has always had a lot less 
memory corruption than C++ (thanks to slices, GC, bounds-checks, 
and default initialization!). And C++ has less corruption than C 
thanks to encapsulation. CVE are often due to C which has the 
maximum number of corruptions.

If one's software is an attack vector, then people that care 
could use the @safe subset instead of making the life of every 
beginner worse.