DIP 1028 "Make @safe the Default" is dead

[Iain Buclaw]

On Friday, 29 May 2020 at 11:04:00 UTC, jmh530 wrote:
> On Friday, 29 May 2020 at 04:53:07 UTC, Walter Bright wrote:
>> [...]
>
> Thank you Walter. I am sure this was not an easy decision, and 
> I respect how you have handled the response.
>
> I think one important takeaway from this should be that people 
> were not opposed to "memory safety by default." Instead, they 
> were opposed to "@safe in its current implementation by 
> default."
>
> In terms of changing the behavior of @safe, I think it would be 
> useful to review comments on this old bug report [1] about 
> changing @safe to a whitelist instead of blacklist. I think if 
> @safe was a whitelist instead of a blacklist, the concerns 
> about @safe's current implementation would be diminished.
>
> I also think some of the comments on the thread discussing the 
> DIP procedure are also relevant for improving the DIP process 
> going forward. In particular, creating a small DIP committee, 
> perhaps consisting of the Language Maintainers, the principal 
> maintainers of LDC and GDC, and maybe one person elected by the 
> community (hopefully Andrei if he has time to volunteer), that 
> would discuss each DIP before voting might help make a more 
> robust decision.

I wouldn't disagree with being made inclusive on the final 
decision making (though in this case I don't think it would have 
changed the outcome).

However, I would regard myself as a language implementer, not a 
language designer (nor library maintainer).