Assign it to a local val first

this was my first thought too, but if you need a function to manage the number of nullables you’re handling at once, all the

val

declarations would probably get unwieldy quickly

I'd argue that if you're touching that many nullables at once something's already a bit fishy.

I'm not sure I follow. It sounds like the function would be more unwieldy. If you're worried the number of `val`s will decrease readability or pollute the scope, you can wrap it in a

run

(which will be inlined).

class Thing(
    var int: Int?,
    var str: String?,
    var char: Char?
) {
  fun frobnicate() {
    run {
      val i = int
      val s = str
      val c = char
      if (i != null && s != null && c != null) {
        
      }
    }
  }
}

vs

class Thing(
    var int: Int?,
    var str: String?,
    var char: Char?
) {
  fun frobnicate() {
    where(int, str, char) { i, s, c ->

    }
}

Ah, I was envisioning something else entirely for some reason. I see your point now.

Ok, being new, i wanted to make sure i wasn't missing any kotlin feature to this