Open DRSchlaubi opened 3 years ago
Thanks for the report! This is a bug reproduced specifically on AtomicBoolean.update [getAndUpdate, updateAndGet]
invocations. Will be fixed by the next release.
Your workaround with wrapping this invocation works for now.
fun setTrue() {
atomicBool.update { true }
}
It only happens if you actually call
block
, andblock
is suspending (both variants of the on function cause it)Also, only AtomicBoolean seems to be affected I couldn't reproduce it with any other type
Using it like this does not bring up the error
Exact error
Maybe related to #39, #123