<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=""><div dir="auto" style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hi,<div class=""><br class=""></div><div class="">When <a href="https://github.com/apple/swift-evolution/blob/master/proposals/0111-remove-arg-label-type-significance.md" class="">SE-0111</a> was approved, I noticed the implication it had when using closures as callbacks:</div><div class=""><br class=""></div><div class="">Writing</div><div class=""><font face="Monaco" class=""> func foo(completion: (success: Bool) -> Void) {</font></div><div class=""><font face="Monaco" class=""> completion(success: true)</font></div><div class=""><font face="Monaco" class=""> }</font></div><div class=""><font face="Monaco" class=""><br class=""></font></div><div class="">is no longer possible, because function types can’t have argument labels anymore, and the function has to be written:</div><div class=""><div class=""><font face="Monaco" class=""> func foo(completion: (Bool) -> Void) {</font></div><div class=""><font face="Monaco" class=""> completion(true)</font></div><div class=""><font face="Monaco" class=""> }</font></div></div><div class=""><font face="Monaco" class=""><br class=""></font></div><div class="">which doesn’t look very nice, especially as the number of the arguments increases.</div><div class=""><br class=""></div><div class="">After talking to Chris Lattner about this, he referred me to <a href="https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20160711/024331.html" class="">this</a> email.</div><div class="">I was wondering if there's been any further work or plans in restoring the use of argument labels in closures.</div><div class=""><br class=""></div><div class="">- Franklin</div></div>
</body></html>