Why does the `.value` property in the MutableStateFlow documentation say that it is thread-safe, wh...

# coroutines

[Lukas Lechner]

Why does the .value property in the MutableStateFlow documentation say that it is thread-safe, when it clearly isn't (when e.g. concurrently increasing an integer value from multiple concurrent coroutines)

[Sam]

By “thread safe” here they just mean that it won’t break when multiple threads use it at the same time.

[Sam]

Incrementing a value really takes two operations; a read and then a write. “Thread-safe” just means that multiple threads can read and write the value concurrently. It doesn’t necessarily guarantee anything about the order that those reads and writes happen in.

[Sam]

If you need atomic increments there is MutableStateFlow.update 👍

[Lukas Lechner]

Thanks @Sam

[statmark56]

Ngl, the last part without external synchronization does sound convincing though that it is thread-safe in general term 🙈