IssueTracker

Sometimes we want to use mutableState() only to be able to safely set values during composition/measure and then have ability to read this value without causing extra remeasure/recomposition. Currently we have to just use regular vars which is not thread-safe and the value will be updated even if the composition is aborted.

We discussed it and though the api could be

fun <T> peekableMutableStateOf(): PeekableMutableState<T>

interface PeekableMutableState<T>: MutableState<T> {
    fun peek(): T
}