newCTFE is getting ported to 2.092

[Stefan Koch]

On Friday, 5 June 2020 at 21:52:05 UTC, Steven Schveighoffer 
wrote:
> On 6/5/20 5:46 PM, Stefan Koch wrote:
>> On Friday, 5 June 2020 at 21:09:37 UTC, H. S. Teoh wrote:
>>> On Fri, Jun 05, 2020 at 08:24:10PM +0000, Stefan Koch via 
>>> Digitalmars-d wrote:
>>>> newCTFE port to 2.092
>>>
>>> How close are we to newCTFE being mergeable?  Been slobbering 
>>> over it since it was first announced way back when, can't 
>>> wait for it to arrive already!
>>>
>> Trust me once it's merged you'll be disappointed because the 
>> problem were templates all along (hence my work on type 
>> functions)
>
> But without newCTFE the cure is worse than the disease.
>
> I think it's going to allow more possibilities of replacing 
> templates with CTFE handling.
>
> I have some ideas to do type functions without specialized 
> compiler support. But I think it would be painful without a 
> better CTFE engine.
>
> -Steve

As long as you code sensibly.
I.E. not relay on the GC for everything or on "~=" to be fast.
Or use library facilities like Appender. (Which are fine for 
runtime but too expensive to be interpreted)

CTFE is really not an issue at all.

But yes, I would like to have newCTFE as a substrate.
And I do want this shadow to be gone :)