Safer D first draft

[Lance Bachmeier]

On Monday, 23 September 2024 at 13:17:23 UTC, Paul Backus wrote:

> 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.

I agree. I'd actually go a bit further and say that if it's 
turned on by default, if anything, the effect would be to give 
users a false sense of security - they'd be confused why checks 
here and there are missing (I certainly wouldn't understand the 
reasoning). As a permanent compiler switch, the opt-in nature 
would prevent confusion, but that wouldn't require a DIP.