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

[12345swordy]

On Tuesday, 17 August 2021 at 14:52:22 UTC, russhy wrote:
> 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

Which is not a inherently an evil thing, so there is no need for 
hyperbolic language such as using the word atrocities. It's all 
about the trade offs.

- Alex