<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="">Proposal link: <a href="https://github.com/apple/swift-evolution/blob/master/proposals/0066-standardize-function-type-syntax.md" class="">https://github.com/apple/swift-evolution/blob/master/proposals/0066-standardize-function-type-syntax.md</a><div class=""><br class=""></div><div class="">Hello Swift community,</div><div class=""><br class=""></div><div class="">The review of SE-0066 “Standardize function type argument syntax to require parentheses” ran from April 25...May 2, 2016. The proposal is <b class="">accepted</b> for Swift 3.</div><div class=""><br class=""></div><div class="">There was a significant amount of feedback on the proposal, with a fairly common theme of “lukewarm acceptance.” A number of community members were sad to see this familiar syntactic shortcut go away, but acknowledge that it fits well with recent directions, e.g., the elimination of the implicit tuple splat behavior (<a href="https://github.com/apple/swift-evolution/blob/master/proposals/0029-remove-implicit-tuple-splat.md" class="">SE-0029</a>). The core team acknowledges that the ability to elide parentheses is not actively harmful to the language, but felt that it was better to have consistency around function types (always have parentheses) than provide a relatively small syntactic shortcut for higher-order functions. The core team did not feel that this proposal needed to include required parentheses within closures, which have their own fairly specific grammar.</div><div class=""><br class=""></div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>- Doug, Review Manager</div><div class=""><br class=""></div></body></html>