<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 Sep 12, 2016, at 3:03 PM, Shyamal Chandra 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="">Instead of moving onto Swift 3, 4, and 5 (with different syntax), why don't you standardize the library and language operations and functions for the different package and frameworks included with Xcode</span></div></blockquote></div><br class=""><div class="">That is the goal, and apparently it will happen with Swift 4. It’s a very large goal, and if you wanted the Swift designers to hold off on releases until it was complete, there’d be no updates to the language for some time. Moreover, outside developers would have no input into the changes going on, unlike the current development process where anyone can suggest and discuss proposals.</div><div class=""><br class=""></div><div class="">Other new languages like Go and Rust have also gone through years of early evolution where syntax and APIs changed incompatibly. (In the case of Go, it happened prior to 1.0 when hardly anyone was paying attention to it.)</div><div class=""><br class=""></div><div class="">—Jens</div></body></html>