Chances of D getting proper runtime reflection?

[Jacob Carlborg]

On 2011-08-22 22:27, Andrei Alexandrescu wrote:
> On 8/22/11 2:22 PM, Jacob Carlborg wrote:
>> On 2011-08-22 21:16, Andrei Alexandrescu wrote:
>>> FWIW I don't think D should pay the cost of reflection up-front and
>>> compulsively for all types.
>>
>> So ClassInfo.getMembers is there because?
>
> At this point the implementation is unclear on what should and what
> shouldn't be part of compiler-supplied metadata.
>
>>> If David's code example is what you have, I don't think Orange got
>>> "making a class serializable" properly yet.
>>>
>>>
>>> Andrei
>>
>> You do understand that this is ONLY necessary when serializing through a
>> base class reference? Other suggestions are welcome.
>
> I do understand that point, which is unrelated to mine.
>
>
> Andrei

Ok, I just want to make sure because I think that the library is working 
pretty well and turned out quite good with the, somewhat, limit 
possibilities the language give you, i.e. no runtime reflection.

-- 
/Jacob Carlborg