Can I use the range operator with if statement in Swift?
Solution 1
You can use the "pattern-match" operator ~=
:
if 200 ... 299 ~= statusCode {
print("success")
}
Or a switch-statement with an expression pattern (which uses the pattern-match operator internally):
switch statusCode {
case 200 ... 299:
print("success")
default:
print("failure")
}
Note that ..<
denotes a range that omits the upper value, so you probably want
200 ... 299
or 200 ..< 300
.
Additional information: When the above code is compiled in Xcode 6.3 with optimizations switch on, then for the test
if 200 ... 299 ~= statusCode
actually no function call is generated at all, only three assembly instruction:
addq $-200, %rdi
cmpq $99, %rdi
ja LBB0_1
this is exactly the same assembly code that is generated for
if statusCode >= 200 && statusCode <= 299
You can verify that with
xcrun -sdk macosx swiftc -O -emit-assembly main.swift
As of Swift 2, this can be written as
if case 200 ... 299 = statusCode {
print("success")
}
using the newly introduced pattern-matching for if-statements. See also Swift 2 - Pattern matching in "if".
Solution 2
This version seems to be more readable than pattern matching:
if (200 ... 299).contains(statusCode) {
print("Success")
}
Solution 3
This is an old thread, but it seems to me we're over-thinking this. It seems to me the best answer is just
if statusCode >= 200 && statusCode <= 299
There's no
if 200 > statusCode > 299
form that I'm aware of, and the other suggested solutions are doing function calls, which are harder to read, and might be slower to execute. The pattern match method is a useful trick to know, but seems like a poor fit for this problem.
Edit:
Personally, I find the pattern match operator to be hideous, and wish the compiler would support if x in 1...100
syntax. That is sooooo much more intuitive and easy to read than if 1...100 ~= x
Solution 4
I wanted to check 4xx errors except 401. Here is the code:
let i = 401
if 400..<500 ~= i, i != 401 {
print("yes")
} else {
print("NO")
}
Solution 5
I preferred Range .contains() operator too, until found that its implementation is inefficient - https://oleb.net/blog/2015/09/swift-ranges-and-intervals/
We can represent the condition x < 0 using a range: (Int.min..<0).contains(x) is exactly equivalent. It is vastly slower, though. The default implementation of contains(_:) traverses the entire collection, and executing a loop nine quintillion times in the worst case is not cheap.
Related videos on Youtube
Comments
-
Jimmy almost 2 years
Is it possible to use the range operator
...
and..<
with if statement. Maye something like this:let statusCode = 204 if statusCode in 200 ..< 299 { NSLog("Success") }
-
Sky almost 10 yearsCool, is this O(1)? Also, it'd be nice if Swift had a short hand for switch statements, like Scala for example. But given that you're always forced to handle all possibilities at compile time in Swift, it may not really be feasible.
-
Martin R almost 10 years@Sky: From the generated assembly code one can see that a library function
func ~= (Range<A>, A) -> Bool
is called. I would assume that this function works with O(1). -
Martin R almost 10 years@Downvoter: Some explaining comment would be nice, so that I can improve or fix the answer ...
-
codester almost 10 years@MartinR how you get to know which function called by assembly language.Hopper? +1 for cool answer
-
Martin R almost 10 years@codester: I compiled the code on the command line with
xcrun -sdk macosx swift -emit-assembly main.swift
and inspected the assembly code. Then I usedxcrun swift-demangle ...
to de-mangle the name of the called function. - Unfortunately, Xcode cannot yet create assembly code for Swift files, perhaps it will work in a later version. -
Duncan C about 9 yearsMartin, where is the "~=" pattern match operator documented? I looked in the Swift Standard Library PDF and there's no mention. I see it referenced in the "Swift Programming Language" iBook, but not defined.
-
Martin R about 9 years@DuncanC: developer.apple.com/library/ios/documentation/Swift/Conceptual/…, section "Expression Pattern": "... By default, the ~= operator compares two values of the same type using the == operator. It can also match an integer value with a range of integers in an Range object, ..."
-
Martin R about 9 yearsYou are right that this version is better to read, I just tried to answer the explicit question "Is it possible to use the range operator ... ?" – But Xcode 6.3 beta (in optimized mode) generates exactly three assembly instructions for
if 200 ... 299 ~= statusCode
, no function call :) -
Martin R about 9 yearsActually
if 200 ... 299 ~= statusCode
gives the same assembly code asif statusCode >= 200 && statusCode <= 299
-
Duncan C about 9 years@MartinR, that's impressive smarts from the compiler! Gotta love LLVM.
-
rickster about 9 yearsUnless this conditional is in a critical section that gets visited thousands of times per second, worrying about function call overhead is premature optimization. Even then, I'd worry more about what a function call is doing rather than the cost of calling it. Nice job @MartinR for proving there's no cost regardless, though.
-
Duncan C about 9 yearsThat's a pretty oblique reference to the pattern-match operator. I was hoping for specific documentation on that operator.
-
Duncan C about 9 years@rickster, true enough. I still tend to prefer efficient constructs over inefficient ones as a matter of habit (assuming readability is similar). Not to the extent that I waste too much of MY time on it, but it still pays to know what the costs of different approaches are.
-
TaylorAllred about 8 yearsI don't know if this is a recent change or not, but ranges can't take spaces. So
200 ... 299
results in a compiler error. But200...299
Does not. I tried to submit an edit, but it was complaining about formatting code blocks for some reason even though all I did was delete the spaces... :/ -
Martin R about 8 years@TaylorAllred:
if case 200 ... 299 = statusCode { ... }
(with spaces) still compiles without problems in my Xcode 7.3. -
TaylorAllred about 8 yearsWeird, OK, I'll do some more testing on my end, thanks for responding
-
ma11hew28 about 8 yearsStylistically, I write ranges without spaces, as does Apple's Swift documentation.
-
ma11hew28 about 8 yearsHow do I do the inverse? Like:
if case 200...299 != statusCode
orif 200...299 ~! statusCode
-
Martin R about 8 years@mattdipasquale: Apart from the obvious
if case 200 ... 299 = statusCode { } else { ... }
or usingguard
there is – as far as I know – no negation of matching operators.if (200...299).contains(statusCode)
works but that is not pattern matching. -
Martin R about 8 years@mattdipasquale: ... I meant
if !(200...299).contains(statusCode)
-
RenniePet over 7 yearsThis is nitpicking, but I disagree with your suggestion that your if statement is more readable or understandable than the answer posted by @SerhiiYakovenko. Simply on the basis of DRY - you name "statusCode" twice. In a late-night bleary-eyed debugging session after I'd decided that a different variable named "statusValue" should be used here instead of "statusCode", I just might make the mistake of changing one of the variable names and not the other.
-
rghome over 7 years@Duncan C - I agree: given two more-or-less equal choices, write the one that executes faster.
-
Nazim Kerimbekov about 6 yearsExactly what I was searching for
-
Ahmadreza over 4 yearsI get this error => Can't form Range with upperBound < lowerBound
-
KPM almost 4 yearsThis information is obsolete, and wrong. It already was wrong at the time you wrote your answer.