For your specific example, I'd 100% use the guard statement. It achieves the same result.<br><br>-1 from me.<br><div class="gmail_quote"><div dir="ltr">On Sat, Dec 12, 2015 at 9:43 AM J. Cheyo Jimenez via swift-evolution <<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">-1 from me. I think I would rather have an if-then expression that would handle both False and True cases. <div><a href="https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20151207/001944.html" target="_blank">https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20151207/001944.html</a><br><div><br></div><div>Also, in most cases I feel that guard would be a better choice. <div><br></div><div><br></div></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Dec 12, 2015 at 5:39 AM, James Campbell via swift-evolution <span dir="ltr"><<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I propose adding the unless and if statements from ruby.<br>
<br>
Return false if james = nil<br>
<br>
This returns false if the variable James is nil<br>
. This line does it unless james is nil:<br>
<br>
Return false unless james = nil<br>
<br>
This has been really handy when working in ruby, reduces lines and pyramids of doom<br>
<br>
Sent from my iPhone<br>
_______________________________________________<br>
swift-evolution mailing list<br>
<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a><br>
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br>
</blockquote></div><br></div>
<img src="https://u2002410.ct.sendgrid.net/wf/open?upn=QOj-2FXWMwrtGhHdk0ao-2FYqYPqIFSXRT0DG7Sea-2BCcxJN8c5RRhyvxdcersifGUQfEvSKA-2BcBWhD1IL2gdIk1Z0CqzR9cyYlLS6x2ISqAdFeWy8udykQsTYlY5El02WDIqpG7sRXq-2BJZwOCAxhwCrfyRgVMAG6-2FcFCyxFMDMuAC2m2vuiSL3IEmYfF1-2BnU827NC1-2FOUujQ-2B1nncjE3VhzlbBhcHN6AHbj9MPAYz-2B8du-2BQ-3D" alt="" width="1" height="1" border="0" style="min-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">
_______________________________________________<br>
swift-evolution mailing list<br>
<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a><br>
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br>
</blockquote></div>