hey folks, is this a known issue/feature? ```kotl...

# announcements

[Nikolay Kasyanov]

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

[robstoll]

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"
        }
    )

[robstoll]

you could write the following if you want the let :

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

[robstoll]

your code is the same as :

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

[Nikolay Kasyanov]

I see, so let “binds” to the latest if-else subexpression?

[robstoll]

exactly

[Nikolay Kasyanov]

@robstoll thank you!

[pivovarit]

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

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

[Nikolay Kasyanov]

this let behaviour still feels counterintuitive though 😅

[SiebelsTim]

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

[louiscad]

Using an extension on an else expression without parentheses is not good for readability IMHO

[ribesg]

else if is not elif for a reason 🙂