Do you guys actually use the

3. The Smart-Cast Elvis Operator approach

? (You have two number threes btw). I understand that it's less characters, but you still have to translate it to the good old

if

when reading the code, right?

I think I can read

couldBeNullMesage ?: return

… It’s almost like reading Java ternary…

trueOrFalse ? doOnTrue : doOnFalse;

hmm that explains it..I hate ternary operator 😄

i have used this feature from time to time, yes

yep, I totally agree, I think Swift should have gone by automatically return if null. The point of writing

guard

is pretty useless otherwise

you may wish to do something else before returning, like logging or throwing an error

and then you would write

@Steve, to print something, just use

couldBeNullMesage ?: run { println("hello there"); return }