https://learn.staticvar.dev/courses/jetpack-compose-internals/06-invalidation-recomposition-skipping/Recent content in Invalidation, recomposition, and skipping on Staticvar LearnHugo -- gohugo.ioen-ushttps://learn.staticvar.dev/courses/jetpack-compose-internals/06-invalidation-recomposition-skipping/01-a-state-write-targets-observed-scopes/Mon, 01 Jan 0001 00:00:00 +0000https://learn.staticvar.dev/courses/jetpack-compose-internals/06-invalidation-recomposition-skipping/01-a-state-write-targets-observed-scopes/Status: A read creates an observation edge and a later write can target the scopes on that edge. That causal model is Durable . The queue names and handoff methods are Version-specific at the pinned AndroidX revision. Outcome Name the recipient of a state change at each boundary: snapshot notification, known composition, observed restart scope, and recomposer work list. Say what has not happened yet. The write does not invalidate the whole tree During composition, CompositionImpl.https://learn.staticvar.dev/courses/jetpack-compose-internals/06-invalidation-recomposition-skipping/02-conditional-and-imminent-invalidation/Mon, 01 Jan 0001 00:00:00 +0000https://learn.staticvar.dev/courses/jetpack-compose-internals/06-invalidation-recomposition-skipping/02-conditional-and-imminent-invalidation/Status: “Invalidated” is not one timing category. The four outcomes are Version-specific names for a Durable distinction between queued and active work. Outcome Interpret IGNORED, SCHEDULED, DEFERRED, or IMMINENT, and explain why a derived-state read can remain conditionally tracked. Four outcomes The pinned InvalidationResult enum defines these meanings (Composer.kt): Result Meaning in the pinned runtime IGNORED The scope is removed, not yet entered, or cannot recompose. SCHEDULED The composition is not composing; the invalidation is recorded for later work.https://learn.staticvar.dev/courses/jetpack-compose-internals/06-invalidation-recomposition-skipping/03-stability-becomes-comparison-metadata/Mon, 01 Jan 0001 00:00:00 +0000https://learn.staticvar.dev/courses/jetpack-compose-internals/06-invalidation-recomposition-skipping/03-stability-becomes-comparison-metadata/Status: Stability is compiler/runtime protocol input, not reflection. Its promise model is Durable ; inferred categories, fields, comparisons, and mask positions are Version-specific . Outcome Explain why a parameter gets equality or identity comparison, and describe dirty masks as per-parameter metadata rather than memorize their packing. Inference is more than “stable or unstable” The pinned compiler represents stability as Certain, Runtime, Unknown, Parameter, or Combined (Stability.kt). Primitives, strings, functions, enums, and objects can be known stable; mutable backing properties can make a class unstable; generic and external types can remain runtime or uncertain.https://learn.staticvar.dev/courses/jetpack-compose-internals/06-invalidation-recomposition-skipping/04-skipping-is-a-decision-not-a-guarantee/Mon, 01 Jan 0001 00:00:00 +0000https://learn.staticvar.dev/courses/jetpack-compose-internals/06-invalidation-recomposition-skipping/04-skipping-is-a-decision-not-a-guarantee/Status: Restartability gives the runtime a callable scope to revisit. Execution is a separate Durable decision; gates and strong-skipping defaults are Version-specific . Outcome Explain why a restartable composable can execute, skip, or be deliberately non-skippable. Restartable is a return path A restart group records a RecomposeScopeImpl and a callback that can re-enter it. The pinned compiler emits startRestartGroup, a body, and endRestartGroup()?.updateScope (ComposableFunctionBodyTransformer.kt). That answers “can this region restart?