Thanks for sharing that, Slava! Reading that really helped me gain a better
understanding of how the current reflection model works and how it could be
extended.
Although my intended use cases are more for in-process type-level
reflection akin to objc_copyClassList and class_copyPropertyList.
In
Hi Jean-Pierre,
> On Dec 7, 2015, at 12:21 PM, Jean-Pierre Simard via swift-dev
> wrote:
>
> > Note that I'm already working on this part. The Swift runtime needs to
> > provide low-level reflection interfaces that allow the standard library to
> > implement Mirror without depending on priva
> Note that I'm already working on this part. The Swift runtime needs to
provide low-level reflection interfaces that allow the standard library to
implement Mirror without depending on private runtime ABI.
That's great to hear! Is there any chance that this work could introduce
type-level reflect
> On Dec 6, 2015, at 2:20 AM, Dmitri Gribenko via swift-dev
> wrote:
>
> We need new runtime entry points that make sense for the new mirror
> implementation. The current entry points (the _reflect() function and
> all its implementation details) directly depend on the old mirrors.
> This step
