Andrei Alexandrescu wrote: > A tool could repeatedly run > the compiler with -v and see what modules it couldn't load, to > then download them.
This is what my build.d does. <http://arsdnet.net/dcode/build.d> There's a problem though: it's pretty slow. You always run the compiler at least twice with this setup with any libs - once to get the dependencies and build the compile line, once to actually compile. If there's nested dependencies, it just gets worse. Build into the compiler, and the speed ought to be improvable by several times.
