News for hackers. Stuff that matters.

A comment on D Language accepted for inclusion in GCC. Parent comment

Re:D Language accepted for inclusion in GCC by dgfgfdagasdfgfa on Wednesday June 21, 2017 @06:39PM (#14608591)
How is D's memory safety without the GC? How does it guarantee you don't use-after-free, de-ref nulls, buffer overflow, etc?
[ Parent | on HN ]
Re:D Language accepted for inclusion in GCC by WalterBright on Wednesday June 21, 2017 @07:19PM (#14608857)
Great question! The answer is a bit more than a simple reply can do, so:

Pointers Gone Wild: Memory Safety and D http://dconf.org/2017/talks/bright.html

[ Parent | on HN ]
Re:D Language accepted for inclusion in GCC by hellcatv on Wednesday June 21, 2017 @08:51PM (#14609318)
It seems like use-after-free is still a potential issue, even with those guard rails. Rust deals with those through named lifetimes --would those ideas be useful in D as well?
[ Parent | on HN ]
Re:D Language accepted for inclusion in GCC by dgfgfdagasdfgfa on Wednesday June 21, 2017 @07:31PM (#14608932)
Walter, you're always so responsive in these threads! Cheers.
[ Parent | on HN ]
Re:D Language accepted for inclusion in GCC by mhh__ on Wednesday June 21, 2017 @07:19PM (#14608859)
This is being worked on, but there is already memory safety checks implemented in the compiler (That one can use now) "-dip1000"
[ Parent | on HN ]