CTFE Status

[Stefan Koch via Digitalmars-d]

On Thursday, 10 November 2016 at 20:15:49 UTC, Jonathan M Davis 
wrote:
> On Thursday, November 10, 2016 18:40:03 Stefan Koch via 
> Digitalmars-d wrote:
>> On Thursday, 10 November 2016 at 01:17:48 UTC, Stefan Koch 
>> wrote:
>> > After the bad news now a bit of good news.
>> > I just finished the strCat algorithm;
>> >
>> > [...]
>>
>> As expected this code is slightly wrong and will fail on the
>> offset == 3 case.
>> It will need a little bit of tinkering until it's ready to go 
>> :)
>
> And aren't you glad that you have all of these unit tests to 
> verify that what you're working works properly? They don't 
> necessarily catch everything, but it would be _way_ worse to 
> completely replace something like this without them. :)
>
> The way that D promotes unit testing is definitely one of its 
> strong points.
>
> - Jonathan M Davis


I love compile-time unitests.
Who does not like them ?

The interpret3.d test in the compiler acceptance testsuite is 
almost a work of art.
After you pass that one you can be pretty sure to have a 
complainant d compiler.

The current Status of stringCat can be found here :
https://gist.github.com/UplinkCoder/fed000f5ca41ad3d65d59a7a63d5ef6f