Implementing serialisation with minmal boilerplate and template overhead using core.reflect

[russhy]

On Tuesday, 17 August 2021 at 14:16:52 UTC, 12345swordy wrote:
> On Tuesday, 17 August 2021 at 13:52:19 UTC, russhy wrote:
>> Is this runtime reflection?
>>
>> Will this depend on the GC? if so does it add pressure to the 
>> GC?
>>
>> We already have compile time type introspection, i don't think 
>> it's wise to move things to runtime, we have a poor GC adding 
>> more pressure to it is just bad
>>
>> Compile time reflection already proved to be superior in heavy 
>> workloads
>>
>> Never been a fan of runtime reflection in java/c#, not good 
>> examples to follow
>>
>> Also if it uses the GC, i'm not sure "core" package is the go, 
>> should be put on "std", or as a library imo
>
> The reason that they use runtime reflection in java/c# is 
> because of the basic principles of OOP.
>
> -Alex

As well as other atrocities such as runtime code generation / 
runtime dependencies


> It's for introspecting over code at compile time, not at 
> runtime. Stefan and I have been mulling over this for ages and 
> I think we both think it can do more than reflection as 
> currently know it at least. This let's you drink from the 
> firehose, so to speak.

Oh i see, so the goal is not what i was thinking, my bad!

I guess will have to read the DIP to know more about it, that is 
interesting, i'm curious now