Is "<donut hole skipping>" impossible without MutableState? Put another way: if I have a composable...

# compose

[jeff]

Is "donut hole skipping" impossible without MutableState?

Put another way: if I have a composable whose only argument is a "normal" class Input (i.e. not a MutableState), and all of the sub-composables are based on fields from Input :
Can any of the sub-composables inside it be recomposed without recomposing the parent? If so I'd love to see an example, because I can't seem to concoct one.

[tad]

I believe marking Input as @Stable would allow for this, but the docs don't make it entirely clear.

[tad]

State<T> is just the explicit easy to pass around a value without causing recompositions, which is what I expect Stable to mean. Otherwise it comes down to how Input.equals is implemented, I believe.