Blog Post: What Does Memory Safety Really Mean in D?
Dennis
dkorpel at gmail.com
Thu Aug 27 14:10:36 UTC 2020
On Thursday, 27 August 2020 at 13:32:44 UTC, Paul Backus wrote:
> Of course, you could also argue that these are things that
> shouldn't be allowed in @safe code to begin with--regardless of
> whether pointers are involved.
I did not intend to argue anything with that post, I was just
pointing out the limitations of the workaround if it were used
today, in case Dukc wasn't aware of them.
> I think presenting @system variables as "protection" against
> memory corruption is the wrong way frame the discussion.
Is that still in reply to me (or DIP1035)? I don't recall saying
something like that and don't want to get the wrong message
across. I agree with everything you just wrote.
More information about the Digitalmars-d-announce
mailing list