DIP 1021--Argument Ownership and Function Calls--Final Review

Timon Gehr timon.gehr at gmx.ch
Fri Sep 20 01:41:41 UTC 2019

On 20.09.19 03:17, Timon Gehr wrote:
> P.S. I've encouraged people for the last 10 years to submit proposals on 
> how to make D memory safe.

BTW: The problem is not that D is not memory safe. The "problem" is that 
D relies on GC to be memory safe. There may be some @trusted code that 
uses manual memory management and violates @safe D memory safety, but 
that is not the fault of the language specification. To solve the 
problem you need to give more tools to this currently broken @trusted 
code so it can restrict @safe code suitably in it's usage patterns, not 
destroy GC and all the actually @safe code that has been written so far.

More information about the Digitalmars-d mailing list