proposal: private module-level import for faster compilation

deadalnix via Digitalmars-d digitalmars-d at puremagic.com
Wed Jul 20 12:11:56 PDT 2016


On Wednesday, 20 July 2016 at 07:45:12 UTC, Timothee Cour wrote:
> currently, top-level imports in a module A are visible by other 
> modules B importing A, and are visited (recursively) during 
> compilation of A, slowing down compilation and increasing 
> dependencies (eg with separate compilation model, a single file 
> change will trigger a lot of recompilations).
>

That is purely an implementation problem. SDC doesn't have this 
problem for instance as it only parse/analyze import on demand.

modules imported by A are already not visible to B, but still 
required sometime to compile B to resolve A's signatures.

Implementation problem should not be "fixed" by changing the 
language.



More information about the Digitalmars-d mailing list