Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

@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.


Not much of the library is dependent on the GC. For example, only one of the algorithms is.


There'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




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: