<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="">Do you mean you want a default closure?<div class=""><br class=""></div><div class="">func forEach<U,T>(transform: (U)->T = { return $0 }, do: (T)->Void)</div><div class=""><br class=""></div><div class="">doSomething { </div><div class=""> if let g = $0 as? Giraffe { g.eatTheTallLeaves() } </div><div class="">}</div><div class=""><br class=""></div><div class="">doSomething(transform: { $0 as! Giraffe }) { </div><div class=""> $0.eatTheTallLeaves() </div><div class="">}</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 6 Jan 2017, at 15:28, Jay Abbott 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="">Some good arguments regarding warnings and multiple closures. But I can't help that feel when designing an API, if you have to add a convenience method that takes just one closure simply to call the real method, this is exactly the sort of boilerplate code that default arguments are supposed to replace.<br class=""></div><br class=""><div class="gmail_quote"><div dir="ltr" class="">On Thu, 5 Jan 2017 at 05:48 Douglas Gregor <<a href="mailto:dgregor@apple.com" class="">dgregor@apple.com</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word" class="gmail_msg"><div class="gmail_msg"><blockquote type="cite" class="gmail_msg"><div class="gmail_msg">On Jan 4, 2017, at 9:44 PM, Saagar Jha <<a href="mailto:saagar@saagarjha.com" class="gmail_msg" target="_blank">saagar@saagarjha.com</a>> wrote:</div><br class="gmail_msg m_-994319049499522620Apple-interchange-newline"><div class="gmail_msg"><div style="word-wrap:break-word" class="gmail_msg">So, then this should have a warning? I’m still not getting one.<div class="gmail_msg"><br class="gmail_msg"></div><div class="gmail_msg">func foo(a: () -> (), b: (() -> ())? = nil, c: Int) {</div><div class="gmail_msg"><span class="m_-994319049499522620Apple-tab-span gmail_msg" style="white-space:pre-wrap"> </span>a()</div><div class="gmail_msg"><span class="m_-994319049499522620Apple-tab-span gmail_msg" style="white-space:pre-wrap"> </span>b?()</div><div class="gmail_msg">}</div><div class="gmail_msg"><br class="gmail_msg"></div><div class="gmail_msg">foo(a: {</div><div class="gmail_msg"><span class="m_-994319049499522620Apple-tab-span gmail_msg" style="white-space:pre-wrap"> </span>print(“Bar”)</div><div class="gmail_msg">}, c: 0)</div><div class="gmail_msg"><br class="gmail_msg"></div></div></div></blockquote><div class="gmail_msg"><br class="gmail_msg"></div></div></div><div style="word-wrap:break-word" class="gmail_msg"><div class="gmail_msg">If you give “c” a default value (e.g., “= 0”), it will give a warning.</div><div class="gmail_msg"><br class="gmail_msg"></div><div class="gmail_msg">I’m happy for the warning to get more eager, so long as it also gets a Fix-It at the same time.</div><div class="gmail_msg"><br class="gmail_msg"></div><div class="gmail_msg"><span class="m_-994319049499522620Apple-tab-span gmail_msg" style="white-space:pre-wrap"> </span>- Doug</div></div><div style="word-wrap:break-word" class="gmail_msg"><div class="gmail_msg"><br class="gmail_msg"><blockquote type="cite" class="gmail_msg"><div class="gmail_msg"><div style="word-wrap:break-word" class="gmail_msg"><div class="gmail_msg"><div class="gmail_msg"><span style="font-family:'SF UI Text';font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important" class="gmail_msg">Saagar Jha</span><br style="font-family:'SF UI Text';font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px" class="gmail_msg"><br style="font-family:'SF UI Text';font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px" class="gmail_msg"><br style="font-family:'SF UI Text';font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px" class="gmail_msg">
</div>
<br class="gmail_msg"><div class="gmail_msg"><blockquote type="cite" class="gmail_msg"><div class="gmail_msg">On Jan 4, 2017, at 9:34 PM, Douglas Gregor <<a href="mailto:dgregor@apple.com" class="gmail_msg" target="_blank">dgregor@apple.com</a>> wrote:</div><br class="gmail_msg m_-994319049499522620Apple-interchange-newline"><div class="gmail_msg"><div style="word-wrap:break-word" class="gmail_msg"><br class="gmail_msg"><div class="gmail_msg"><blockquote type="cite" class="gmail_msg"><div class="gmail_msg">On Jan 4, 2017, at 9:32 PM, Saagar Jha <<a href="mailto:saagar@saagarjha.com" class="gmail_msg" target="_blank">saagar@saagarjha.com</a>> wrote:</div><br class="gmail_msg m_-994319049499522620Apple-interchange-newline"><div class="gmail_msg"><div style="word-wrap:break-word" class="gmail_msg"><br class="gmail_msg"><div class="gmail_msg">
<br class="gmail_msg m_-994319049499522620Apple-interchange-newline"><span style="font-family:'SF UI Text';font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important" class="gmail_msg">Saagar Jha</span><br style="font-family:'SF UI Text';font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px" class="gmail_msg"><br style="font-family:'SF UI Text';font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px" class="gmail_msg"><br style="font-family:'SF UI Text';font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px" class="gmail_msg">
</div>
<br class="gmail_msg"><div class="gmail_msg"><blockquote type="cite" class="gmail_msg"><div class="gmail_msg">On Jan 4, 2017, at 8:35 PM, Douglas Gregor <<a href="mailto:dgregor@apple.com" class="gmail_msg" target="_blank">dgregor@apple.com</a>> wrote:</div><br class="gmail_msg m_-994319049499522620Apple-interchange-newline"><div class="gmail_msg"><div style="font-family:SFUIText-Regular;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px" class="gmail_msg"><br class="gmail_msg m_-994319049499522620Apple-interchange-newline">On Jan 4, 2017, at 7:48 PM, Saagar Jha via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="gmail_msg" target="_blank">swift-evolution@swift.org</a>> wrote:<br class="gmail_msg"><br class="gmail_msg"></div><blockquote type="cite" style="font-family:SFUIText-Regular;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px" class="gmail_msg"><div class="gmail_msg">Check out <a href="https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20160606/020470.html" class="gmail_msg" target="_blank">this thread</a>–it’s very similar to what you proposed, but it didn’t go anywhere. FWIW +1 to this as well as the ability to use multiple trailing closures like so:<div class="gmail_msg"><br class="gmail_msg"></div><div class="gmail_msg">animate(identifier: “”, duration: 0, update: {</div><div class="gmail_msg"><span class="m_-994319049499522620Apple-tab-span gmail_msg" style="white-space:pre-wrap"> </span>// update</div><div class="gmail_msg">}, completion: {</div><div class="gmail_msg"><span class="m_-994319049499522620Apple-tab-span gmail_msg" style="white-space:pre-wrap"> </span>// completion</div><div class="gmail_msg">}</div><div class="gmail_msg"><div class="gmail_msg"><br class="gmail_msg m_-994319049499522620Apple-interchange-newline"><span style="font-family:'SF UI Text';font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important" class="gmail_msg">Saagar Jha</span><br style="font-family:'SF UI Text';font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px" class="gmail_msg"><br style="font-family:'SF UI Text';font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px" class="gmail_msg"><br style="font-family:'SF UI Text';font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px" class="gmail_msg"></div><br class="gmail_msg"><div class="gmail_msg"><blockquote type="cite" class="gmail_msg"><div class="gmail_msg">On Jan 4, 2017, at 6:25 PM, Jay Abbott via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="gmail_msg" target="_blank">swift-evolution@swift.org</a>> wrote:</div><br class="gmail_msg m_-994319049499522620Apple-interchange-newline"><div class="gmail_msg"><div dir="ltr" class="gmail_msg"><div class="gmail_msg m_-994319049499522620markdown-here-wrapper"><p style="margin:0px 0px 1.2em!important" class="gmail_msg">When you have a function with a closure and then another optional default<span class="gmail_msg m_-994319049499522620Apple-converted-space"> </span><code style="font-size:1em;font-family:Consolas,Inconsolata,Courier,monospace;margin:0px 0.15em;padding:0px 0.3em;white-space:pre-wrap;border:1px solid rgb(234,234,234);background-color:rgb(248,248,248);border-top-left-radius:3px;border-top-right-radius:3px;border-bottom-right-radius:3px;border-bottom-left-radius:3px;display:inline" class="gmail_msg">= nil</code><span class="gmail_msg m_-994319049499522620Apple-converted-space"> </span>closure at the end, like this:</p><pre style="font-family:Consolas,Inconsolata,Courier,monospace;font-size:1em;line-height:1.2em;margin:1.2em 0px" class="gmail_msg"><code class="gmail_msg m_-994319049499522620hljs m_-994319049499522620language-swift" style="font-size:1em;font-family:Consolas,Inconsolata,Courier,monospace;margin:0px 0.15em;white-space:pre-wrap;overflow:auto;border-top-left-radius:3px;border-top-right-radius:3px;border-bottom-right-radius:3px;border-bottom-left-radius:3px;border:1px solid rgb(204,204,204);padding:0.5em;color:rgb(51,51,51);background-image:none;background-color:rgb(248,248,248);display:block!important;background-position:0% 0%;background-repeat:repeat repeat">open <span class="gmail_msg m_-994319049499522620hljs-keyword" style="color:rgb(51,51,51);font-weight:bold">static</span> <span class="gmail_msg m_-994319049499522620hljs-func"><span class="gmail_msg m_-994319049499522620hljs-keyword" style="color:rgb(51,51,51);font-weight:bold">func</span> <span class="gmail_msg m_-994319049499522620hljs-title" style="color:rgb(153,0,0);font-weight:bold">animate</span><span class="gmail_msg m_-994319049499522620hljs-params">(identifier: String,
duration: Double,
update: @escaping AnimationUpdate,
completion: AnimationCompletion? = <span class="gmail_msg m_-994319049499522620hljs-built_in" style="color:rgb(0,134,179)">nil</span>)</span> </span>{
</code></pre><p style="margin:0px 0px 1.2em!important" class="gmail_msg">You can’t use trailing closure syntax for the<span class="gmail_msg m_-994319049499522620Apple-converted-space"> </span><code style="font-size:1em;font-family:Consolas,Inconsolata,Courier,monospace;margin:0px 0.15em;padding:0px 0.3em;white-space:pre-wrap;border:1px solid rgb(234,234,234);background-color:rgb(248,248,248);border-top-left-radius:3px;border-top-right-radius:3px;border-bottom-right-radius:3px;border-bottom-left-radius:3px;display:inline" class="gmail_msg">update</code><span class="gmail_msg m_-994319049499522620Apple-converted-space"> </span>argument when leaving the<span class="gmail_msg m_-994319049499522620Apple-converted-space"> </span><code style="font-size:1em;font-family:Consolas,Inconsolata,Courier,monospace;margin:0px 0.15em;padding:0px 0.3em;white-space:pre-wrap;border:1px solid rgb(234,234,234);background-color:rgb(248,248,248);border-top-left-radius:3px;border-top-right-radius:3px;border-bottom-right-radius:3px;border-bottom-left-radius:3px;display:inline" class="gmail_msg">completion</code><span class="gmail_msg m_-994319049499522620Apple-converted-space"> </span>argument out/default.</p><p style="margin:0px 0px 1.2em!important" class="gmail_msg">This kind of breaks one of the benefits of default arguments, which is that you can add them to existing released functions without breaking the calling code. This means you have to add a separate convenience function without the extra argument, which is annoying and inelegant.</p></div></div></div></blockquote></div></div></div></blockquote><div style="font-family:SFUIText-Regular;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px" class="gmail_msg">Why not simply add the "completion" parameter before the trailing closure? That would still allow existing callers to work, without having to change the language. </div><br style="font-family:SFUIText-Regular;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px" class="gmail_msg"><blockquote type="cite" style="font-family:SFUIText-Regular;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px" class="gmail_msg"><div class="gmail_msg"><div class="gmail_msg"><div class="gmail_msg"><blockquote type="cite" class="gmail_msg"><div class="gmail_msg"><div dir="ltr" class="gmail_msg"><div class="gmail_msg m_-994319049499522620markdown-here-wrapper"><p style="margin:0px 0px 1.2em!important" class="gmail_msg">Another annoying thing is that you can easily miss this error if you happen to not use trailing closure syntax in your tests or other usage, because adding the extra default argument compiles fine for code that uses normal syntax.</p></div></div></div></blockquote></div></div></div></blockquote><div style="font-family:SFUIText-Regular;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px" class="gmail_msg">The Swift compiler warns when a parameter written as a closure type isn't the last parameter. The warning is actually disabled in the specific case above because you've written it using a typealias... maybe we should warn on such cases (it's worth a bug report). Regardless, in the majority of instances, you'll get a warning, so it won't be silent on disabling trailing closure syntax. </div></div></blockquote><div class="gmail_msg"><br class="gmail_msg"></div><div class="gmail_msg">Tried this out in the playground:</div><div class="gmail_msg"><br class="gmail_msg"></div><div class="gmail_msg">func foo(a: () -> (), b: (() -> ())? = nil) {</div><div class="gmail_msg"><span class="m_-994319049499522620Apple-tab-span gmail_msg" style="white-space:pre-wrap"> </span>a()</div><div class="gmail_msg"><span class="m_-994319049499522620Apple-tab-span gmail_msg" style="white-space:pre-wrap"> </span>b?()</div><div class="gmail_msg">}</div><div class="gmail_msg"><br class="gmail_msg"></div><div class="gmail_msg">foo(a: {</div><div class="gmail_msg"><span class="m_-994319049499522620Apple-tab-span gmail_msg" style="white-space:pre-wrap"> </span>print(“Bar”)</div><div class="gmail_msg">})</div><div class="gmail_msg"><br class="gmail_msg"></div><div class="gmail_msg">and didn’t receive a warning for it, either.</div></div></div></div></blockquote></div><br class="gmail_msg"><div class="gmail_msg">We don’t warn here because ‘foo’ does have a trailing closure… it’s for the second parameter. I guess we could still warn about ‘a’ (maybe lump it into the same bug about the typealias case).</div><div class="gmail_msg"><br class="gmail_msg"></div><div class="gmail_msg"><span class="m_-994319049499522620Apple-tab-span gmail_msg" style="white-space:pre-wrap"> </span>- Doug</div><div class="gmail_msg"><br class="gmail_msg"></div></div></div></blockquote></div><br class="gmail_msg"></div></div></div></blockquote></div><br class="gmail_msg"></div></blockquote></div>
_______________________________________________<br class="">swift-evolution mailing list<br class=""><a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a><br class="">https://lists.swift.org/mailman/listinfo/swift-evolution<br class=""></div></blockquote></div><br class=""></div></body></html>