Does the compiler always semantically analyze everything in a project?

[Marco Leise via Digitalmars-d-learn]

Specifically, when I put some code in a separately compiled
lib, does that save me anything in terms of files that have to
be analyzed or will dmd always go through every file that can
be reached through includes ? (.di files are out of question,
because they have issues)

-- 
Marco

Re: Does the compiler always semantically analyze everything in a project?

[Dicebot via Digitalmars-d-learn]

Apart from unused templates - yes. In abscence of .di files 
separate compilation only affects generated object files

Re: Does the compiler always semantically analyze everything in a project?

[Marco Leise via Digitalmars-d-learn]

Am Thu, 13 Nov 2014 16:54:45 +
schrieb "Dicebot" :

> Apart from unused templates - yes. In abscence of .di files 
> separate compilation only affects generated object files

I thought so and wonder how that will scale with large code
bases. Lately I found so many bugs and shortcomings that the
ice is growing thin. There's bugs with .di files, with
separate compilation, with SIMD, static dtors inside
templates... and no the uncertainty how D projects will scale
if the module with main imports the world. It makes me want to
switch to C++. :p
I hope Walter's idea of full lazy evaluation can help here.

-- 
Marco