https://learn.staticvar.dev/courses/jetpack-compose-internals/09-moving-reusing-nesting-composition/Recent content in Moving, reusing, and nesting composition on Staticvar LearnHugo -- gohugo.ioen-ushttps://learn.staticvar.dev/courses/jetpack-compose-internals/09-moving-reusing-nesting-composition/01-movable-content-carries-identity/Mon, 01 Jan 0001 00:00:00 +0000https://learn.staticvar.dev/courses/jetpack-compose-internals/09-moving-reusing-nesting-composition/01-movable-content-carries-identity/Evidence legend: Durable marks a stable mental model; Version-specific marks behavior tied to the AndroidX pin below; Experimental marks a changing or transitional path. A remember value normally follows its position in one composition. What if a screen changes from a row to a column, but the editor, focus, or scroll state must follow the content rather than the old branch? movableContentOf makes that relocation explicit: the call creates a tracked content identity, and a later call can claim the state and nodes that left another location.https://learn.staticvar.dev/courses/jetpack-compose-internals/09-moving-reusing-nesting-composition/02-reusable-composition-and-node-lifecycle/Mon, 01 Jan 0001 00:00:00 +0000https://learn.staticvar.dev/courses/jetpack-compose-internals/09-moving-reusing-nesting-composition/02-reusable-composition-and-node-lifecycle/Evidence legend: Durable marks a stable mental model; Version-specific marks behavior tied to the AndroidX pin below; Experimental marks a changing or transitional path. Movable content answers “how do I keep this identity while its location changes?” Reuse answers “how do I avoid allocating a new compatible node for different content?” The second question deliberately has a different answer for remembered values: node structure may be recycled, while remembered slots are treated as invalid for the new content.https://learn.staticvar.dev/courses/jetpack-compose-internals/09-moving-reusing-nesting-composition/03-composition-context-and-measure-time-subcomposition/Mon, 01 Jan 0001 00:00:00 +0000https://learn.staticvar.dev/courses/jetpack-compose-internals/09-moving-reusing-nesting-composition/03-composition-context-and-measure-time-subcomposition/Evidence legend: Durable marks a stable mental model; Version-specific marks behavior tied to the AndroidX pin below; Experimental marks a changing or transitional path. A subcomposition is a separate Composition, but it should not become a separate universe. A child may need values from the parent, and a parent state write may need to invalidate the child. CompositionContext is the bridge: it preserves logical ownership while allowing a layout to calculate child content later than the parent content call.https://learn.staticvar.dev/courses/jetpack-compose-internals/09-moving-reusing-nesting-composition/04-subcompose-slots-precomposition-and-pausing/Mon, 01 Jan 0001 00:00:00 +0000https://learn.staticvar.dev/courses/jetpack-compose-internals/09-moving-reusing-nesting-composition/04-subcompose-slots-precomposition-and-pausing/Evidence legend: Durable marks a stable mental model; Version-specific marks behavior tied to the AndroidX pin below; Experimental marks a changing or transitional path. SubcomposeLayoutState is not just a map from IDs to lambdas. At the pinned source, LayoutNodeSubcompositionsState keeps virtual child LayoutNodes and a NodeState for each composition. Its child list has exactly three storage ranges: active children, a reusable middle section, and precomposed children waiting at the end (SubcomposeLayout.