In what scenario should I use `remember { state }` rather than just `state` ? I have tried and my ap...

# compose

[tjohnn]

In what scenario should I use remember { state } rather than just state ? I have tried and my app works thesame way.

[Adam Powell]

that depends on what state is. Do you have a more specific example?

[tjohnn]

The state is a mutableStateOf<SomeDataClass>() @Adam Powell

[tjohnn]

And the state is created from StateFlow.observeAsState()

[Adam Powell]

you do not need to remember it yourself then

[Adam Powell]

observeAsState is responsible for maintaining its persistence guarantees across recomposition

[tjohnn]

Okay thanks. Can you share a resource on remember{}, I’m still confused on it

[Adam Powell]

I'm looking around to see what we have published, the kdocs on remember itself are kind of thin at the moment

[Adam Powell]

a way to think about it is that it creates an instance field for a composable

[Adam Powell]

generally speaking you should remember things you create and want to persist across recompositions, and count on other composable functions to do the same

[tjohnn]

Okay thank you, I think I got it to some extent, would research more