[swift-evolution] Location of ! in Boolean negation expressions

Johannes Neubauer johannes.neubauer at udo.edu
Sat Aug 6 17:52:59 CDT 2016

I think your syntax is too near to forced unwrapping. It's just do I put the ! Before or after the dot. This becomes even harder to read if you want to use both at the same time. Then you end up with !.!

Further on, if you want to negate a complete expression, the ! Is again before the parentheses. This will "look" inconsequent.

Last but not least it is uncommon.

All the best 

Von meinem iPhone gesendet

> Am 06.08.2016 um 09:37 schrieb Darren Mo via swift-evolution <swift-evolution at swift.org>:
> Consider code like
> guard !parameters.contains(where: { !validValueRange.contains($0) }) else …
> Oftentimes I need to write negation expressions like this. The location of the exclamation marks really bugs me when writing and reading this code. The natural English ordering would be something like
> “Make sure parameters does not contain an element such that validValueRange does not contain this element.”
> But the programming-language-imposed ordering is
> “Make sure NOT parameters contains an element such that NOT validValueRange contains this element.”
> See how much harder the programming language version is to understand? Most of the time I write the positive version first because it comes out so naturally, and then I add the exclamation marks afterwards. It really burdens my mind every time I need to write code like this. Let’s come up with a solution to address this!
> Here’s my zero-thought solution:
> guard parameters.!contains(where: { validValueRange.!contains($0) }) else …
> I’d love to hear alternate solutions and whether other people are having this problem too!
> Darren
> _______________________________________________
> swift-evolution mailing list
> swift-evolution at swift.org
> https://lists.swift.org/mailman/listinfo/swift-evolution

More information about the swift-evolution mailing list