On 17 Jul 2014 13:40, "w0rp via Digitalmars-d" <[email protected]> wrote: > > The key to making D's GC acceptable lies in two factors I believe. > > 1. Improve the implementation enough so that you will only be impacted by GC in extermely low memory or real time environments. > 2. Defer allocation more and more by using ranges and algorithms more, and trust that compiler optimisations will make these fast. >
How about 1. Make it easier to select which GC you want to use at runtime init. 2. Write an alternate GC aimed at different application uses (ie: real-time) We already have (at least) three GC implementations for D. Regards Iain
