theapache64
03/13/2022, 11:40 AMrememberUpdateState
I’ve seen most of the @Composables
are using rememberUpdateState
before invoking a lambda.
For eg, BackHandler
internally calling rememberUpdateState
on onBack
lambda, clickable
modifier calls on onClick
lambda.
Does that mean we should wrap all lambda with rememberUpdateState
before invoking ? 🤔
If that’s the case, why can’t compiler do it for us?
#possibly_a_stupid_questionAlbert Chang
03/13/2022, 11:47 AMrememberUpdatedState
quite clearly.theapache64
03/13/2022, 11:59 AMrememberUpdateState
with LaunchedEffect
. But what am asking is, basically we use rememberUpdateState
to get the latest value (or to avoid stale value). Is there a scenario where we need to access the stale value? 🤔Albert Chang
03/13/2022, 12:04 PMrememberUpdatedState
.theapache64
03/13/2022, 12:09 PMonClick
, onBack
etc.
So lambas without rememberUpdatedState
should be very rare?Albert Chang
03/13/2022, 12:15 PMtheapache64
03/13/2022, 12:34 PMrememberUpdatedState
if and only if am accessing a lambda in an area where recomposition can’t be reached. For example, remember
, LaunchedEffect
, etc.. is that what you’re saying ?Albert Chang
03/13/2022, 12:35 PMremember
, it's better to just use it as a key.theapache64
03/13/2022, 12:37 PMrememberUpdateState
because its DisposableEffect
?rememberUpdateState
here.Albert Chang
03/13/2022, 12:43 PMOnBackPressedDispatcher
is designed that way.theapache64
03/13/2022, 12:44 PMrocketraman
03/14/2022, 1:47 AM