On 2011-08-15 01:39, Jonathan M Davis wrote
That's just not going to work. If you use .di files, you lose CTFE and inlining
for anything which isn't in the .di files. As such, there's a definite advantage
for a library to _not_ use .di files. There have been some suggestions about
how to fix that, but it's pretty much been decided to put off fixing how .di 
files
to D3.

How about putting the complete source code in the .di files and then the compiler will still be able to do CTFE and inline? But that might be no difference compared with a .d file.

So, libraries _must_ be able to use .d files exclusively. With D2, we _cannot_
assume that libraries will use .di files. There's a good chance that they
won't. Maybe they will for D3 but not for D2.

- Jonathan M Davis


--
/Jacob Carlborg

Reply via email to