Re:DConf 2019 in London
by atilaneves on Monday February 18, 2019 @12:27PM
(#19192323)
Yes, it's the case in practice: I've written a lot of @nogc code. Some parts of the standard library require the GC, but not all of it, and the parts that I usually use are fine (std.algorithm, std.range, ...).
Since allocators landed, it's been a lot easier, and I've written a library that does C++-style smart pointers for D:
Honest question: is it the case in practice though? Last time I checked D, you could disable the GC in theory, but in practice many things would fail to work, most importantly their standard library. As this been fixed since then?