<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=""><br class=""><div><blockquote type="cite" class=""><div class="">On Jun 27, 2016, at 8:30 AM, Daniel Dunbar via swift-users <<a href="mailto:swift-users@swift.org" class="">swift-users@swift.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><span style="font-family: Alegreya-Regular; font-size: 15px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">No, this is not possible. All of the code in a single process needs to be compiled with the same version of Swift.</span><br class="Apple-interchange-newline"></div></blockquote></div><br class=""><div class="">How long will this be the case? The product I work on is distributed primarily as a compiled framework. If we port any of it to Swift we’d first need some assurance of binary compatibility.</div><div class=""><br class=""></div><div class="">(Also, if you really mean <i class="">all</i> of the code in a process, that implies that Apple can’t implement any system frameworks in Swift. So it seems that this question ties in with the earlier one of “how long do we have to copy multi-megabyte compatibility shim libraries into our apps that use Swift?”)</div><div class=""><br class=""></div><div class="">((At the risk of sounding flamey: this sort of confirms my rule of thumb that Swift version numbers have their decimal points misplaced. IMHO, ABI stability is a requirement for a true 1.0 release of a language that has dynamic loading.))</div><div class=""><br class=""></div><div class="">—Jens</div></body></html>