<https://medium.com/@elye.project/kotlins-elvis-be...

# feed

[elye]

https://medium.com/@elye.project/kotlins-elvis-better-than-swift-s-guard-53030d403c3f?source=friends_link&amp;sk=bf7fced446cc161095a9d281054fb927

[Milan Hruban]

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?

[elye]

I think I can read couldBeNullMesage ?: return … It’s almost like reading Java ternary…
trueOrFalse ? doOnTrue : doOnFalse;

[Milan Hruban]

hmm that explains it..I hate ternary operator 😄

[thana]

i have used this feature from time to time, yes

[elect]

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

[Steve]

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

[elect]

and then you would write

[elye]

@Steve, to print something, just use

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