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

[rikki cattermole]

On 04/01/2020 11:42 PM, Atila Neves wrote:
> 
> I get the impression that most of the negative feedback here falls into 
> the following categories:
> 
> 1) This will break too much code
> 2) Crappy code is ok, don't burden users to make their code @safe
> 3) It's too much effort to convert existing code to @safe

There is a solution to all three of the categories that you have 
described that would be of major benefit to D over all. And it has not 
been posted on this thread yet.

We defer this going live till D3.

This way we can do a big push for all the changes that have the 
potential for changing workflows and limitations of existing code while 
ensuring a massive announcement when we have got everything ready to be 
used.

There would still be the preview switch, but it won't be made the 
default by itself. It would be grouped into a new switch ``-preview=d3`` 
and when we are ready we can turn that on by default instead.

Lets tell a story about how to do memory safety, that gives us 
headlines. Lets not do stuff that causes people pain that they are not 
fully on board with.