is there any specific reason for that

# getting-started

[Florian]

is there any specific reason for that

[Dominaezzz]

= is a statement and not an expression.

[Dominaezzz]

So b = 3 doesn't evaluate to any value.

[Dominaezzz]

This decision was made mostly to allow for named parameters.

[Dominaezzz]

var b = 4
fun max(a: Int, b: Int): Int = TODO()

max(a = 2, b = 5)

This would be ambiguous to the compiler, if = was an expression.

[Florian]

ok thank you

[andym]

It also prevents accidental assignment.

[andym]

The following is valid Java, but probably not what you meant:

boolean isSomeCondition = checkSomeCondition();
        if (isSomeCondition = checkSomeOtherCondition()) {
            // isSomeCondition now has the 2nd value:  it was accidentally assigned, instead of just compared
        }

[andym]

In Kotlin, this accidental assignment doesn't compile because if() needs an expression.

[Florian]

yes that makes sense

[Florian]

thanks