<div dir="ltr">`var isFalse: Bool` seems like a nice resolution to me. no need for new keywords and it reads better than !foo</div><div class="gmail_extra"><br><div class="gmail_quote">On Sun, May 22, 2016 at 3:28 AM, Haravikk 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"><div style="word-wrap:break-word"><div>I think this would make more sense if we were to get more characters in operators, such that we could also replace && with and, and || with or, this way we could make not an operator and write expressions like so:</div><div><br></div><div><font face="Monaco"><span style="white-space:pre-wrap"> </span>if foo and not bar { … }</font></div><div><br></div><div>Otherwise as others have said this seems strange as a method. If you don’t find the leading exclamation mark very readable then you could instead do:</div><div><br></div><div><font face="Monaco"><span style="white-space:pre-wrap"> </span>foo != true</font></div><div><br></div><div>It’s a few more characters, but it exists now and reads logically I think.</div><br><div><blockquote type="cite"><div><div class="h5"><div>On 21 May 2016, at 15:50, Антон Миронов via swift-evolution <<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>> wrote:</div><br></div></div><div><div><div class="h5"><div style="word-wrap:break-word">I found negation operator (!) the least detectable among the code. So I’ve decided to add property “not” to BooleanType (Swift 2.2) or Boolean on 3.0 with extension:<div><br></div><div>extension BooleanType {</div><div><span style="white-space:pre-wrap"> </span>var not: Bool { return !self.boolValue }</div><div>}<br><div><div><br></div><div>This is code with negation operator:</div><div><span style="white-space:pre-wrap"> </span>return !self.lanes[position.y][currentLaneRange].contains(.Gap)</div></div></div><div><div><div><br></div><div>As I sad before negation operation is hard to spot. Moreover at first it looks like I’m trying to negate self for some reason.</div><div><br></div><div>This is code with “not” property:</div><div><span style="white-space:pre-wrap"> </span>return self.lanes[position.y][currentLaneRange].contains(.Gap).not</div></div></div><blockquote style="margin:0 0 0 40px;border:none;padding:0px"><div><br></div></blockquote><div><div>Now it is easy to spot the statement I am actually getting negation of.</div><div>On my experience negation operator can occasionally be missed while reading code. This happens less often with “not” property. So I’m proposing to add this property to standard library and prefer it in most cases.</div><div><br></div><div>Thanks,</div><div>Anton Mironov</div></div><div><br></div></div></div></div><span class="">_______________________________________________<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></span></div></blockquote></div><br></div><br>_______________________________________________<br>
swift-evolution mailing list<br>
<a href="mailto:swift-evolution@swift.org">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>
<br></blockquote></div><br></div>