<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 Aug 4, 2017, at 9:16 AM, Mathew Huusko V 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="">Per <a href="https://lists.swift.org/pipermail/swift-evolution-announce/2016-July/000233.html" class="">https://lists.swift.org/pipermail/swift-evolution-announce/2016-July/000233.html</a>, the removal of parameter labels entirely was accepted as a temporary loss for Swift 3 as a means to remove them from the type system. I'm wondering if they're coming back (syntactically) any time soon?</div></div></blockquote><div><br class=""></div><div>The planning approach for Swift 5 hasn’t been announced yet, but it should be soon-ish.</div><div><br class=""></div><div>Responding to the rest of your email in broad terms: there will always be a ton of things that are important and interesting to tackle. There is also a long road ahead of Swift, so prioritization is not a bad thing: just because something doesn’t happen “now” doesn’t mean it never will.</div><div><br class=""></div><div>I would also argue that it would be *bad* for the language to evolve too fast. Landing 20 major features all in the same year runs the very high risk that they doesn’t work well together and don’t have time to settle out properly. It is far more important for Swift to be great over the long term than to have any individual little feature “now”.</div><div><br class=""></div><div>-Chris</div><div><br class=""></div></div><br class=""></body></html>