oh yay I just got to my first "a mutable property that could have been changed by this time" error.

use

let

yeah, that looks like it's probably the best option for this case

make a new val and make it equal the var

@keturn you can't declare that in kotlin

Isn’t there something in contracts that is going to help with that?

Not for mutable values

@keturn even if it was possible, it opens the door for bugs say if someone new to the code base didn't understand that single threaded assumption. Compile time constructs are a bliss

Kotlin won't have such a feature in the near future, because it can lead to nasty bugs when the compiler can't prove that the annotation is still correct https://youtrack.jetbrains.com/issue/KT-20294

To keep it a compile-time construct the compiler would somehow have to be able to trust that the object was thread-local. (or if shared, the only thread that may mutate it is the current thread) and yeah it may well be we don't have any way to communicate that in an enforceable way to the compiler.

Why does the property have to be

var

?