So I was reading through the Compose runtime code and while looking at

withMutableSnapshot

(which has been mentioned here several times) I saw a little note at the end of the doucmentation:

[block] must not suspend if [withMutableSnapshot] is called from a suspend function.

Why is that? 🤔 Is it because other code can be run on the same thread when the

block

suspends resulting in other unrelated part of the app being in this snapshot? I am not sure I know enough about Compose and Coroutines to be sure.

Yes, it's driven by a form of ThreadLocal and we don't have a wiring from this API to a CoroutineContext-based management of it

I see, thanks for the quick response 👌 So would this be OK? (even though it doesn't really make sense)

var state by mutableStateOf(0)
val snap = Snapshot.takeMutableSnapshot()

snap.enter { state = 1 }

val result = suspendWhileGettingNumber()

snap.enter { 
    if (result > 5) state = result
}

snap.apply()

Yes, that general pattern will work fine