News for hackers. Stuff that matters.

A comment on Inside D's GC. Parent comment

Re:Inside D's GC by amelius on Tuesday June 20, 2017 @11:32AM (#14595377)
> The D language is currently heading towards deterministic and safe memory management, making it possible to avoid the GC overall

Is this really true?

[ Parent | on HN ]
Re:Inside D's GC by WalterBright on Tuesday June 20, 2017 @03:53PM (#14597966)
Yes. I gave a presentation on this at DConf 2017.

http://dconf.org/2017/talks/bright.html

[ Parent | on HN ]
Re:Inside D's GC by amelius on Tuesday June 20, 2017 @04:00PM (#14598039)
But is it really possible to completely avoid the GC? I'm thinking of memory blocks with cyclic references, and stuff like that.
[ Parent | on HN ]
Re:Inside D's GC by mhh__ on Tuesday June 20, 2017 @12:57PM (#14596253)
Yes, but the D community isn't structured enough to have such a specific goal. The main effort that I can think of is dip1008, which aims to add reference counted exceptions (Thus eliminating one of the few truly difficult things to get around, e.g. @nogc exceptions require user cooperation else memory gets leaked)
[ Parent | on HN ]