> On Mar 26, 2016, at 5:47 PM, Maury Markowitz via swift-users
> <[email protected]> wrote:
>
> Before I stick my head into the other list, consider:
>
> if statusCode >= 200 && statusCode <= 299
>
> I'm sure examples of something like this occur throughout your code. But the
> actual semantics of the test is hidden here, you're really testing if
> statusCode lies within a range. Swift 2.0 has a couple of options for this,
> but I find them all rather odd. The most recommended is:
>
> if case 0...100 = someInteger
>
> This syntax has problems. For one thing, it's written backwards compared to
> most people's code...
>
> if someinteger == 100
>
How about
if (200..<299).contains(statusCode)
_______________________________________________
swift-users mailing list
[email protected]
https://lists.swift.org/mailman/listinfo/swift-users
