A modern programming language that makes developers happier.

kotlinlang

I would expect .not() and ! to have the same experience, but it looks like they are not. We got an internal discussion that there is not type casting with `not` and it doesn’t lead to `short circuit in a boolean evaluation`. The last one is probably expected since it has only sense for boolean type and you can have not operator for other types.

Yeah, there was `not` involved in the boolean expression with `or` operator

so it works as expected :slightly_smiling_face:

yep, when it's true, the second part doesn't run :slightly_smiling_face: