D not considered memory safe

[H. S. Teoh]

On Fri, Jul 19, 2024 at 04:03:42PM +0000, Lance Bachmeier via Digitalmars-d wrote:
> On Friday, 19 July 2024 at 14:57:17 UTC, Quirin Schroll wrote:
> 
> > This is the single best reason to enable `@safe` by default.
> 
> It's also a good example of the pointless debates that go on around
> here. I know language design is hard. This is not, however. Leave D as
> unsafe by default and add a switch to enable it, or make it safe by
> default and add a switch to disable it. It doesn't matter.
> 
> It's been debated for years and the solution is trivial. In the
> meantime, the rest of the programming world has been advancing. This
> should have been a ten minute decision.

This is typical of the D development process.  Easy decisions are hard,
and hard decisions are impossible.  This is why after more than a decade
we still don't have a good story for `shared`, while a 10-minute
decision like @safe by default has been held up for years simply because
of a trivial disagreement (Walter wants @safe to apply to everything,
include extern(C), everyone else disagrees on the extern(C) part). In
all likelihood it will be another decade before we get @safe by default.

I'm rather tempted to throw my weight behind Adam's fork at this
point...


T

-- 
I am Ohm of Borg. Resistance is voltage over current.