<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div><blockquote type="cite" class=""><div class="">On Nov 14, 2017, at 2:36 PM, Joe Groff via swift-dev <<a href="mailto:swift-dev@swift.org" class="">swift-dev@swift.org</a>> wrote:</div><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><p style="color: rgb(17, 17, 17); font-family: "Helvetica Neue", Helvetica, Arial, Verdana, sans-serif; word-wrap: break-word; margin: 1.3125em 0px; font-size: 1.1429em; line-height: 1.3125em;" class="">The type metadata that gets emitted for struct, enum, and class types includes a reference to a <strong style="line-height: 1;" class="">nominal type descriptor</strong>. The descriptor carries information that pertains to the nominal type declaration itself, independent of specific instantiations of generic types, as well as information that’s of a more “reflective” nature which isn’t on the fast path for compiler-generated code but may be of interest to reflection APIs or one-time initialization actions. The current nominal type descriptor format is lacking in a number of ways that I’d like to improve:</p></div></div></blockquote>Great write-up. Your plan sounds spot-on to me.</div><div><br class=""></div><div>John.</div></body></html>