<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 2016-02-09, at 22:08:16, Thorsten Seitz 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 style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: 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;" class=""><blockquote type="cite" class=""><div class="msg-quote" data-mce-style="word-wrap: break-word;" style="word-wrap: break-word;"><div class=""><br class="Apple-interchange-newline">I’m not sure where I stand on the switch-less case-list closure, but I am afraid that providing such dedicated closure syntax may set a precedent and cause others to want yet another dedicated closure syntax for their own goal; how do we consider a special closure syntax as acceptable, how many of them are too many.<span class="Apple-converted-space"> </span></div></div></blockquote></div><div style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: 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;" class=""><span class=""><br data-mce-bogus="1" class=""></span></div><div style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: 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;" class=""><span class="">Fair enough.</span></div></div></blockquote></div><br class=""><div class="">The `case` inside a closure is not a new concept. Scala (among I think a few other functional languages) implements `case` as a partial function inside closures. </div><div class=""><br class=""></div><div class="">I actually use it quite widely, but not as often as I would use it if it were in Swift - since Scala also implements a match expression (which for the most part would be the same as the match function in Swift - with the exception that it does not need function brackets). </div><div class=""><br class=""></div><div class="">Given that at most we will get a match expression or the partial function `case` structure - I would prefer the `case` structure because it gives us both. </div><div class=""><br class=""></div><div class=""><br class=""></div></body></html>