<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 Oct 11, 2016, at 4:48 PM, Xiaodi Wu via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">Additional info for your reference:<div class=""><br class=""></div><div class="">* Chris Lattner's original email on additional goals and non-goals for Swift 4:</div><div class=""><a href="https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20160725/025676.html" class="">https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20160725/025676.html</a><br class=""></div><div class=""><br class=""></div></div></div></blockquote><br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class="">* Chris Lattner's speculation that Swift 3.x will be time-based: whatever's accepted for Swift 4 and done by spring will ship:</div><div class=""><a href="https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20160725/025722.html" class="">https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20160725/025722.html</a><br class=""></div></div></div></blockquote><br class=""></div><div>Xiaodi is right. I (still) expect that we’ll have a Spring release of Swift, and it will include whatever features happen to be done and good to go whenever it needs to branch (including work that doesn’t involve evolution proposals, like improved compile time, better error messages, etc). </div><div><br class=""></div><div>Overall, we’re not managing a specific feature set goal for it, we’re just treating it as an incremental step along the way to Swift 4.</div><div><br class=""></div><div>-Chris</div><br class=""></body></html>