compose-composition-core

Fix unnecessary recomposition by deferring state reads into provider-lambda modifier overloads, shrinking the restart scope so Compose only re-renders layout or drawing phases instead of whole composable scopes.

derivedStateOf triggers excess invalidation because recomposition relies on snapshot state reads, not parameter changes; passing changing parameters as keys avoids the stale closure trap so recomputation happens only when the computed result changes.

Prevent LazyList item identity bugs by supplying stable keys at the call site rather than relying on index-based identity, which stops cascading invalidations and protects component identity during list updates.

Yes, this approach applies to both Jetpack Compose and Compose Multiplatform development, enforcing composition-time stability rules and Strong Skipping Mode concepts to minimize unnecessary updates across platforms.

Choose state lifetime by matching remember, rememberSaveable, or rememberSerializable to your specific requirements for recomposition, configuration changes, and process death to avoid stale closures and state identity bugs.

You should restrict CompositionLocal usage when it causes excess invalidation or unpredictable recomposition scopes, applying composition-time rules to ensure state reads and stability do not trigger cascading UI updates.