> 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 reflection APIs that would allow reflecting uninstantiated
types? Or should I make a formal proposal for this functionality in
swift-evolution?

On Mon, Dec 7, 2015 at 9:01 AM, Joe Groff via swift-dev <[email protected]
> wrote:

>
> > On Dec 6, 2015, at 2:20 AM, Dmitri Gribenko via swift-dev <
> [email protected]> 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 is slightly harder, but not doesn't require extraordinary
> > skills.  This part requires writing a proposal, because the runtime
> > API is going to be stable.
>
>
> 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.
>
> -Joe
> _______________________________________________
> swift-dev mailing list
> [email protected]
> https://lists.swift.org/mailman/listinfo/swift-dev
>
_______________________________________________
swift-dev mailing list
[email protected]
https://lists.swift.org/mailman/listinfo/swift-dev

Reply via email to