<div dir="ltr">> 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.<div><br></div><div>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?</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Dec 7, 2015 at 9:01 AM, Joe Groff via swift-dev <span dir="ltr"><<a href="mailto:swift-dev@swift.org" target="_blank">swift-dev@swift.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=""><br>
> On Dec 6, 2015, at 2:20 AM, Dmitri Gribenko via swift-dev <<a href="mailto:swift-dev@swift.org">swift-dev@swift.org</a>> wrote:<br>
><br>
> We need new runtime entry points that make sense for the new mirror<br>
> implementation. The current entry points (the _reflect() function and<br>
> all its implementation details) directly depend on the old mirrors.<br>
> This step is slightly harder, but not doesn't require extraordinary<br>
> skills. This part requires writing a proposal, because the runtime<br>
> API is going to be stable.<br>
<br>
<br>
</span>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.<br>
<br>
-Joe<br>
<div class="HOEnZb"><div class="h5">_______________________________________________<br>
swift-dev mailing list<br>
<a href="mailto:swift-dev@swift.org">swift-dev@swift.org</a><br>
<a href="https://lists.swift.org/mailman/listinfo/swift-dev" rel="noreferrer" target="_blank">https://lists.swift.org/mailman/listinfo/swift-dev</a><br>
</div></div></blockquote></div><br></div>