Safer D first draft

[Paul Backus]

On Monday, 23 September 2024 at 12:43:03 UTC, Walter Bright wrote:
> On 9/23/2024 5:24 AM, Paul Backus wrote:
>> Does that mean this is intended to be a transitional feature 
>> to help users migrate their code to a future @safe-by-default 
>> edition of D? Or are we giving up on @safe-by-default, and 
>> replacing it with this proposal?
>
> It means our current method of all-or-nothing with @safe is a 
> bridge too far for a lot of code.
>
> Whether it is transitional or not, the more errors detected at 
> compile time, the better.

In that case, I'm strongly opposed to this.

Fundamentally, this proposal does nothing to make writing @safe 
code easier; it just makes writing non- at safe code more annoying. 
It's the bad part of @safe-by-default without the good part.

If you're looking for a less all-or-nothing approach to 
increasing the adoption of @safe, allow me to once again 
recommend universal attribute inference:

https://forum.dlang.org/thread/pfawiqhppkearetcrkno@forum.dlang.org