<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 class="">I'm conflicted.</div><div class=""><br class=""></div><div class="">Pros:</div><div class=""><br class=""></div><div class="">1) Neat. :-)</div><div class=""><br class=""></div><div class="">2) Um, less typing? But Xcode has snippets, you know.</div><div class=""><br class=""></div><div class="">3) Less visual noise? Perhaps someone considers that visual noise, but to me { return nil } is an essential part of the flow and actually helps to understand it.</div><div class=""><br class=""></div><div class="">4) I would love a “guard!” variant that crashes instead of returning.</div><div class=""><br class=""></div><div class="">Cons:</div><div class=""><br class=""></div><div class="">1) Can no longer find all returns by just looking for 'return'.</div><div class=""><br class=""></div><div class="">2) Reads more like an assertion than like a return.</div><div class=""><br class=""></div><div class="">I believe there are no good arguments one way or another, so we have to fall back on the taste of the core team.</div><div class=""><br class=""></div><div class="">A.</div><div class=""><br class=""></div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Dec 17, 2015, at 2:35 PM, Kevin Ballard 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="">
<title class=""></title>
<div class=""><div class="">On Wed, Dec 16, 2015, at 04:30 PM, Erica Sadun via swift-evolution wrote:<br class=""></div>
<blockquote type="cite" class=""><div class="">Count me in as a "no". Despite the redundancy, actually spelling out how the else clause leaves scope is valuable to reading the code.<br class=""></div>
</blockquote><div class=""> </div>
<div class="">Agreed. Count me as a "no" as well. `else { return }` is not problematic enough to justify the penalty to reading comprehension.<br class=""></div>
<div class=""> </div>
<div class="">-Kevin Ballard</div>
<img src="https://u2002410.ct.sendgrid.net/wf/open?upn=LRtxqIpN0uduUbaiFaLozLZv7i-2BSLNOBgkrlBNK2PSV1VWlXmepjDuQQRACRORIPoBUfg6gQNOKT3g6twNv1bBSO1nhocOMtjx0IR-2BwSwJkU4YfB20Lg2SVGjLermrW4qcYRRkmoWiVCfE5qKJc9ZHi1lBUNlzhbXQK5QWvtf7QXcD6qP3iCZvJN-2BdQ318m7aig9xUzbdxfmUe8gzjAhf-2B5OKGUKfpCE09Akh4tW-2BHE-3D" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;" class="">
</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>