A modern programming language that makes developers happier.

kotlinlang

When using `ComposeView` is it generally a bad practice to call `setContent` multiple times?
My worry is that doing that will not trigger a recomposition (based on the existing content set in the previous `setContent` call) but rather a full composition from scratch.

It triggers a recomposition based on the previous state of the composition like any other mutableStateOf snapshot state change; ComposeView.setContent just sets a `mutableStateOf&lt;@Composable () -&gt; Unit&gt;` to the function you pass it

If it's a different instance of the same function you'll get a pretty standard recomposition and probably a lot of skipping. If it's a different content function altogether then it will be composing as new content into the same composition