• Marco Leise (7/7) Nov 13 2014 Specifically, when I put some code in a separately compiled
• Dicebot (2/2) Nov 13 2014 Apart from unused templates - yes. In abscence of .di files
• Marco Leise (12/14) Nov 13 2014 I thought so and wonder how that will scale with large code

Marco Leise <Marco.Leise gmx.de> writes:

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

"Dicebot" <public dicebot.lv> writes:

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

Marco Leise <Marco.Leise gmx.de> writes:

Am Thu, 13 Nov 2014 16:54:45 +0000
schrieb "Dicebot" <public dicebot.lv>:

 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