CTFE and DI: The Crossroads of D

[Steven Schveighoffer]

On Thu, 10 May 2012 10:47:59 -0400, Andrei Alexandrescu  
<SeeWebsiteForEmail at erdani.org> wrote:

> On 5/10/12 6:17 AM, Steven Schveighoffer wrote:
>> On Wed, 09 May 2012 23:00:07 -0400, Andrei Alexandrescu
>> <SeeWebsiteForEmail at erdani.org> wrote:
>>> Actually the point here is to still be able to benefit of di automated
>>> generation while opportunistically marking certain functions as "put
>>> the body in the .di file".
>>
>> If you aren't going to strip the files, I don't see the point in it.
>
> Inlining.

No, I mean if dmd -H isn't going to strip the files, what is the point of  
dmd -H?  I can already copy the .d to .di and have inlining/ctfe, or  
simply use the .d directly.

At this point, in order to get CTFE to work, you have to keep just about  
everything, including private imports.  If we want to ensure CTFE works,  
dmd -H becomes a glorified cp.  If we have some half-assed guess at what  
could be CTFE'd (which is growing by the day), then it's likely to not fit  
with the goals of the developer running dmd -H.

-Steve