Out of curiosity, is this output always guaranteed across Kotlin JVM, Android, JS, Native, etc? I'm ...

# announcements

[janvladimirmostert]

Out of curiosity, is this output always guaranteed across Kotlin JVM, Android, JS, Native, etc?
I'm assuming Kotlin breaks up those ++i and i++ into separate lines?

var i = 0
val map = mutableMapOf<String, Int>()
(1..10).forEach {
   map["${++i}"] = ++i + i++
}
println(map)

{1=4, 4=10, 7=16, 10=22, 13=28, 16=34, 19=40, 22=46, 25=52, 28=58}

To ask it differently, is the IR being generated always such that map[...] evaluates first, then the ++i and then the i++ ?

[Vampire]

I hope so. The language should define the semantics, not the underlying system it is compiled to. If the result is not reliably identical, I'd call that a bug.

[Nir]

Although, allowing such code to pass review is also a bug 🙂

[Nir]

In C++ where undefined behavior is more common (to allow for optimizations), answering a question like the above requires a PhD

[janvladimirmostert]

yes, it's horrible code and if that was C++, the answer would probably depend on which compiler and which flags you're using

I'm curious if Kotlin does something with such code so that it executes predictably on all platforms it compiles to

[Nir]

I'm actually shocked that kotlin supports both ++i and i++

[Vampire]

Why? sometimes you need either, sometimes the other

[Nir]

post increment is just kind of confusing a source of bugs, in C and C++.

[Nir]

Even in C++ where you have to use incrementing far more, it's almost always clearer to just do the increment on its own line

[Vampire]

Every language construct can be confusing and source of bugs if you don't understand and use it properly 😄

[Nir]

In Kotlin I actually would have just made ++ a statement, not an expression. This is consistent with the fact that a += 1 is not an expression (unlike C++)

[Nir]

Sure, but some are more prone than others. A decade of C++ later, I still see people make mistakes with these (sometimes when they are explaining how intuitive they are)

[Nir]

It's also less likely to be clear to the average kotlin dev because it's used far far less, so the rare times it is used, better to be more verbose and clear. In C and C++, you use ++ far more often (for a few reasons)

[Animesh Sahu]

I'm actually shocked that kotlin supports both ++i and i++

Kotlin even has unary operator (like +i -i) 😛