`StateFlow` appears to compare values before updating them (unlike `LiveData`), so if I have a mutab...

# coroutines

[william]

StateFlow appears to compare values before updating them (unlike LiveData), so if I have a mutable list which I update and send to my MutableStateFlow it doesn't get published from the looks of it - unless I create a new list / copy it. Is that the right way to work around this?

[Adam Powell]

Probably yes; consider kotlinx.immutable lists if you find you need to optimize for the costs of copying your particular data set.

[Adam Powell]

Generally speaking, passing mutable data through flows that you continue to mutate after emitting is risky and can lead to problems with multithreading

[william]

yeah for sure. i don't mutate it anyway but its probably good practice regardless

[Adam Powell]

if you're changing the same collection instance before emitting it again, you definitely are mutating it 🙂

[Adam Powell]

those changes will be made out from under any downstream collectors that may have retained that reference for later use

[Adam Powell]

and since many flow operator use async channels as implementation details, it is quite possible for the upstream emit call to complete before the downstream collector begins processing that emitted value

[william]

yeah sorry - i just meant the 'observer' isn't mutating it. but yeah i see

[william]

good thoughts though i will check this out more