The composition local is based on a concept called "composition scope". A composition scope is a set of components that are related to each other. When a component is composed, it's added to a composition scope. The composition local allows components to access information about their composition scope.
If data were a ImmutableList<String> (stable), and the list object is the same as before, Parent would skip recomposition. jetpack compose internals pdf download
If you aren't ready to purchase a full book, these high-quality guides provide similar "internal" insights for free: Jetpack Compose 1.5/1.6 Essentials Preview (PDF) The composition local is based on a concept
To download the PDF guide, simply click on the link below: The UI doesn't "rebuild" from scratch; the runtime
Without these internals, recomposition would be impossible. The UI doesn't "rebuild" from scratch; the runtime uses the slot table to identify exactly which parts of the UI tree changed and only update those nodes.
The runtime is the "brain" that manages the state and life of the UI.
