August 14, 2021
On Saturday, 14 August 2021 at 11:15:50 UTC, Stefan Koch wrote:
> On Friday, 13 August 2021 at 12:51:21 UTC, Adam D Ruppe wrote:
>> [...]
>
> Thanks for your input.
> In the meantime I have been able to reproduce the behavior in a template.
> `WrapperString` in the following gist https://gist.github.com/UplinkCoder/e60584a2c8f46ae4a490117b878ecec1
>
> The performance of the template is roughly 2 times worse when compared to the `core.reflect` solution still.

That's very promising, is this currently relying on your Task work or could it work in the compiler as is?
August 14, 2021
On Saturday, 14 August 2021 at 14:32:08 UTC, max haughton wrote:
> On Saturday, 14 August 2021 at 11:15:50 UTC, Stefan Koch wrote:
>> On Friday, 13 August 2021 at 12:51:21 UTC, Adam D Ruppe wrote:
>>> [...]
>>
>> Thanks for your input.
>> In the meantime I have been able to reproduce the behavior in a template.
>> `WrapperString` in the following gist https://gist.github.com/UplinkCoder/e60584a2c8f46ae4a490117b878ecec1
>>
>> The performance of the template is roughly 2 times worse when compared to the `core.reflect` solution still.
>
> That's very promising, is this currently relying on your Task work or could it work in the compiler as is?

It can be used as is.

The task system is not required.

Since unlike typefunctions is does not relay on partially resolved nodes.

1 2
Next ›   Last »