On 27/12/2011 07:13, . wrote: <snip>
It's just a extended function for compiler to do batch importing. We still can import the modules one bye one, if really caring about the compiling speed. We need another more choice.
True. But maybe the person who wrote a given app didn't care about compiling speed, or has a superfast CPU/hard drive combination so didn't notice it to be slow. And so just imported the whole of druntime, Phobos, Tango, some other library or even a collection of libraries under a common base package. And then a user who has acquired a source distribution of the app finds compilation to take b****y ages. It will take potentially a lot of trial and error to trim the imports down.
As such, I feel it's better not to make it too easy to import an entire package. Rather, leave library writers to write an "all" module if it's useful for the library to have one. Such a thing can also be optimised to import modules in an order that is found to be fast.
Stewart.
