hey folks, is this a known issue/feature?

kotlin
fun main(args: Array<String>) {
    whatever(-2)
    whatever(0)
    whatever(2)
}

fun whatever(input: Int) {
    if (input < 0) {
        "negative"
    } else if (input > 0) {
        "positive"
    } else {
        "zero"
    }.let {
        println(it)
    }
}

prints:

zero
positive

that's normal behaviour, intellij even suggest that you can replace the let statement and instead write:

if (input < 0) {
        "negative"
    } else println(
        if (input > 0) {
            "positive"
        } else {
            "zero"
        }
    )

I see, so let “binds” to the latest

if-else

subexpression?

exactly

@robstoll thank you!

also, the best way to deal with such cascading logic is to use

when

when {
  input < 0 -> "negative"
  input > 0 -> "positive"
  else -> "zero"
}

this

let

behaviour still feels counterintuitive though 😅

It's not let specifically. else if is just an else branch with an if inside of it.

Using an extension on an

else

expression without parentheses is not good for readability IMHO

else if

is not

elif

for a reason 🙂