Compiler patch for runtime reflection

[Gor Gyolchanyan]

I didn't mean reflection for violating access specifications. In that
case, of course, it's error-prone.
What i meant was a set of dynamic counterparts of static features of D:
* Dynamic interfaces
* Dynamic overloading
* Dynamic modules
* ...
That's what i had in mind.

On Tue, Oct 25, 2011 at 8:08 PM, Robert Jacques <sandford at jhu.edu> wrote:
> On Tue, 25 Oct 2011 11:35:42 -0400, Gor Gyolchanyan
> <gor.f.gyolchanyan at gmail.com> wrote:
>>
>> Requiring explicit request for reflection contradicts D's "safety
>> first, performance second" policy.
>
> Umm, it's "safe defaults, performance possible".
>
>> lack of reflection is a safety issue too, because you won't be able to
>> do some checks.
>
> What would you use reflection to check?
>