We need a guard emoji... how about calling itđŸ›‚?<br><br>;)<br><div class="gmail_quote"><div dir="ltr">On Mon, Feb 22, 2016 at 9:25 AM Erica Sadun <<a href="mailto:erica@ericasadun.com">erica@ericasadun.com</a>> wrote:<br></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"><div>> "<span style="white-space:pre-wrap"> a vision of a little guard standing at his guard post checking papers"</span></div><div><span style="white-space:pre-wrap"><br></span></div></div><div style="word-wrap:break-word">Raises hand. Me too. I like my little guard.<div><br></div><div>On the other hand, I'd love if assert/precondition would be combined into a single call, with an optional `forReleaseBuild:` arg (better named) that defaults to false.</div></div><div style="word-wrap:break-word"><div><br><div><br></div><div>-- E</div></div></div><div style="word-wrap:break-word"><div><div><br></div><div><div><blockquote type="cite"><div>On Feb 22, 2016, at 10:07 AM, Shawn Erickson via swift-evolution <<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>> wrote:</div><br><div><div style="white-space:pre-wrap">Ensure(TM) ...has a little much sugar for my wants in a drink<br><br>I get and like the suggestion from a grammar pov however guard is a little more forceful in terminology which aligns with the fact that you cannot proceed past the guard unless the condition is met. (I have a vision of a little guard standing at his guard post checking papers)<br><br>-Shawn</div><br><div class="gmail_quote"><div dir="ltr">On Mon, Feb 22, 2016 at 9:01 AM John Flanagan via swift-evolution <<a href="mailto:swift-evolution@swift.org" target="_blank">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 style="word-wrap:break-word">The functionality of ‘guard’ is great and this proposal has nothing to do with changing that. The only suggestion is that the word ‘ensure’ would better communicate what a ‘guard’ statement does to those encountering it for the first time and would make code more readable in general.<div><br></div><div>Example:</div><div><br></div><div><font face="Courier">ensure foo != nil else {</font></div><div><font face="Courier">  return;</font></div><div><font face="Courier">}</font></div><div><br></div><div>-John</div></div>_______________________________________________<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>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" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br></div></blockquote></div><br></div></div></div></blockquote></div>