← Back to context

Comment by willtemperley

14 hours ago

I'm surprised, guard is really useful, especially when unwrapping optionals. It's terse, explicit and encourages defensive programming.

internal should definitely go though.

3 comments

willtemperley

Reply
cosmic_cheese  14 hours ago

The absence of guard in Kotlin is one of those things that regularly trips me up when bouncing between it and Swift. Rather than Swift losing guard I’d prefer if Kotlin gained it.

  • iamcalledrob  13 hours ago

    I think the ?: operator ends up being a decent alternative, e.g.

      // Swift
  guard let foo = maybeFoo else {
    print("missing foo")
    return false
  }

  // Kotlin
  val foo = maybeFoo ?: run {
    print("missing foo")
    return false
  }

    Unless there's a use case for guard I'm not thinking of

    • cosmic_cheese  4 hours ago

      It’s a decent alternative, but to someone not familiar with the language what’s going on isn’t as clear.