automem

Here is a library for smart pointers: https://github.com/atilaneves/automem

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: https://github.com/atilaneves/automem

That page should be updated. I was suspicious about #3 since classes in D don't necessarily need the GC. For starters D supports C++ classes, so this works: https://gist.github.com/atilaneves/b69ed0399efac21bb7a977afd... I used `scope` with `new` to allocate on the stack, but `emplace` should just work as well to "placement new" a class in malloc'ed memory. #4 is annoying but one could always use the OS threading API. It's doable to write a library solution to do that akin to boost or Qt before C++11. You do it once and it's there. #5 No dynamic arrays are also annoying. But... writing a clone of std::vector isn't hard, and there's a unique array in my automem library that _should_ be usable in betterC (but I haven't checked): https://github.com/atilaneves/automem/blob/master/source/aut... > Another note is that a big thing I'm looking fo