> > > > I really like the idea of simply adding "import myPackage;", behaving > > like your average ".all" module. > > > > Doing it this way solves at least three problems: No more clunky > > maintenance of convenience modules, big modules can later be split up > > into a package without breaking any client code, and we don't have to > > worry about a ".all" module for Phobos anymore (which is a suggestion > > that has been on the table several times). > > I'm not sure if I like that syntax because you wouldn't be able to tell > the difference between importing a package and a module. But perhaps > that's the point. Otherwise I agree.
The compiler should do this. A package is a directory, and a module just a file. When importing a package, the compiler will import all the modules in the package. The user doesn't care about this. ---------- Zhang <bitwo...@qq.com>