<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Swift Foundation has an incomplete implementation of NSClassFromString/NSStringFromClass (link: <a href="https://github.com/apple/swift-corelibs-foundation/blob/master/Foundation/NSObjCRuntime.swift#L230-L282" class="">https://github.com/apple/swift-corelibs-foundation/blob/master/Foundation/NSObjCRuntime.swift#L230-L282</a>) due to a lack of a standardised method of encoding nested Swift classes, nor other Swift types.<br class=""><br class="">I would think that given<br class=""><br class="">module Contacts<br class=""><br class="">class Person {<br class=""><span class="Apple-tab-span" style="white-space: pre;"> </span>struct Address {<br class=""><span class="Apple-tab-span" style="white-space: pre;"> </span><span class="Apple-tab-span" style="white-space: pre;"> </span>class Postcode {}<br class=""><span class="Apple-tab-span" style="white-space: pre;"> </span>}<br class="">}<br class=""><br class="">Postcode would be encoded as Contacts.Person.Address.Postcode. Since it is not possible to have two different types with the same identifier in the same namespace (i.e. an enum/a class/a struct with the same name at the same declaration level) the encoding would similarly be simple. May I proceed under that assumption or are there ABI stability issues I have yet to consider?<br class=""><br class="">Tom</body></html>