I find myself wanting this over and over again. Reading the docs for Orange made me realize, that I'm not alone. What's wrong with having imports like:
import mylibrary.mypackage; replaced with: import mylibrary.mypackage._; or import mylibrary.mypacakge.package; or import mylibrary.mypackage.all; or anything in that fashion? I thing this is a good idea, because it standardizes access to entire packages in cases, where such an access makes sense. Also, there are cases, when some packages and modules aren't meant to be imported. Implementation packages. I suppose the best way to handle this is to generate .di files for the modules, which do need to be imported and distribute those, but it adds complications and limitations. Would it make sense to allow marking modules as private or something to make it only importable from it's own package? private module myimpl; /// implementations Importing a private module from outside of it's immediate package would cause a compilation error. -- Bye, Gor Gyolchanyan.
