@nogc is still a new addition to the language and phobos is not fully flagged with it.
D devs are working on a solution to reduce gc dependence, it's just not quite there yet.
There are gc-less stdlibs here if you want to avoid phobos: <a href="http://wiki.dlang.org/Libraries_and_Frameworks#Alternative_standard_libraries_.2F_runtimes" rel="nofollow">http://wiki.dlang.org/Libraries_and_Frameworks#Alternative_s...</a><p>For game programming you should consider data oriented design. It really helps avoid the gc and makes your code faster and (imo) simpler.<p>Btw: <a href="http://forum.dlang.org/" rel="nofollow">http://forum.dlang.org/</a> is a great place to learn about ongoing development or to ask questions.
For what it is worth, my understanding is that andralex et al are re-engineering the dlang GC: <a href="http://www.reddit.com/r/programming/comments/2g03af/ds_garbage_collector_problem/ckent8c" rel="nofollow">http://www.reddit.com/r/programming/comments/2g03af/ds_garba...</a>
This line also makes me sad<p>> Stopping all other threads than the thread currently trying to allocate GC memory<p>This doesn't need to be the case, and is one of the strengths of garbage collected languages, IMO. Garbage collection can be performed by another cpu asynchronously, essentially making it free.