<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><blockquote type="cite" class="">On Jun 27, 2016, at 8:59 AM, zh ao <<a href="mailto:owenzx@gmail.com" class="">owenzx@gmail.com</a>> wrote:<br class=""><br class="">Not with current Swift 3. Currently, the developing team make efforts on releasing Swift 3 together with iOS 10 and macOS 10.12 in September.<br class=""></blockquote><br class=""><div class="">I know it’s not with Swift 3. Hopefully people on the dev team are thinking farther ahead.</div><div class=""><br class=""></div><div class=""><blockquote type="cite" class=""><blockquote type="cite" class="">The primary goal of this release is to solidify and mature the Swift language and development experience. While source breaking changes to the language have been the norm for Swift 1 through 3, we would like the Swift 3.x (and Swift 4+) languages to be as <b class="">source compatible</b> with Swift 3.0 as reasonably possible.</blockquote></blockquote><br class=""></div><div class="">I’m asking about <i class="">binary</i> compatibility, not source compatibility; they’re not the same. For example, the Objective-C <i class="">language</i> has gone through many major changes since 2001, but the <i class="">runtime</i> has only broken binary compatibility once (and that was done in a way that didn’t affect any existing code, by putting it into the 64-bit transition on OS X and into the brand-new iOS.)</div><div class=""><br class=""></div><div class="">—Jens</div></body></html>