When I call MutableStateFlow.update {}, isn’t function() called on the same thread? I’m running into...

# flow

[Landry Norris]

When I call MutableStateFlow.update {}, isn’t function() called on the same thread? I’m running into an issue when my code looks like the pseudocode in the 🧵

[Solved] function() is called on the same thread, some other code changed my variable that I missed before calling state.update

[Landry Norris]

state.update {
    array.size
}
array = array.dropLast(1)

I would expect that the state gets updated with the previous size of the array, but it seems to use the size after I dropLast.

[bezrukov]

your expectations are correct, something else in your code is different. Minimal reproducible sample will help to understand what's wrong

[Landry Norris]

I’ll see about getting a minimal reproducible example over the weekend. My code is a bit more complicated than what I showed, but only in so much as state.update is in a function foo and array = array.dropLast is in a function bar.

[Landry Norris]

Just looked more through by code. The function that drops the last element also gets called before state.update, so it is expected that the size is minus one.