3 ms·
It doesn't need to be fully nogc. Not using the parts that use the gc will cripple nothing. You'll know which ones use the gc because they won't compile with @n
by WalterBright 4y ago
It doesn't need to be fully nogc. Not using the parts that use the gc will cripple nothing. You'll know which ones use the gc because they won't compile with @nogc.
- dymk 4y ago@nogc is fine, if you're okay with not being able to use large swaths of the standard library, and by extension, most popular D libraries.
- WalterBright 4y agoNot much of the library is dependent on the GC. For example, only one of the algorithms is.
- skl131313 4y agoThere's no "nogc" containers in phobos, or allocators, or an idiomatic way to do safe manual memory management. It expects you to do it the C way. It's also impossible to implement some things because of how D does moving. There's a DIP in the works to change how moving works, but it's overly complicated and bound to introduce even more bugs. https://github.com/dlang/DIPs/blob/master/DIPs/DIP1040.md https://github.com/dlang/DIPs/blob/master/DIPs/DIP1040.md