Mutation ops¶
Five record types describe every change to the native view tree:
create, update, insert, destroy, and set frame. The
Reconciler emits them; the
NativeViewRegistry
applies them.
Batched mutation protocol between the reconciler and native backends.
The reconciler no longer talks to the native layer one call at a time.
Instead, every commit pass produces an ordered list of small mutation
ops referencing integer tags (stable per-view identifiers), and the
whole list is applied in a single
apply_mutations
call. This mirrors React Native's Fabric mounting layer: the diff phase
is pure, and the native side sees one coherent transaction per commit.
Why tags instead of view objects?
- The diff phase runs before any native view exists, so ops cannot reference views directly.
- Tags give the native side a stable identity to key its own view registry, event routing, and animation bookkeeping on.
- A flat list of
(op, tag, payload)tuples is trivially serializable, which keeps the door open for applying mutations from a background thread or through a single JNI/ObjC crossing in the future.
Op ordering rules (the reconciler guarantees these):
- A
CreateOpfor a tag precedes any other op referencing that tag. InsertOpops appear after both the parent and child exist.DestroyOpops are emitted children-first; handlers detach the view from its parent as part of destruction.SetFrameOpops are only emitted for frames that actually changed since the last layout pass (frame diffing).
Classes:
| Name | Description |
|---|---|
CreateOp |
Create a native view for |
UpdateOp |
Apply |
InsertOp |
Ensure the child view sits at |
DestroyOp |
Release the native view registered under |
SetFrameOp |
Position and size the view registered under |
Attributes:
| Name | Type | Description |
|---|---|---|
Mutation |
Union of every op type carried by a commit transaction. |
Mutation
module-attribute
¶
Union of every op type carried by a commit transaction.
CreateOp
dataclass
¶
Create a native view for tag of element type type_name.
Attributes:
| Name | Type | Description |
|---|---|---|
tag |
int
|
Unique integer identity assigned by the reconciler. |
type_name |
str
|
Element type name (e.g. |
props |
Dict[str, Any]
|
Initial clean props; callables have already been
routed to the |
UpdateOp
dataclass
¶
Apply changed_props to the view registered under tag.
Removed props are signaled with a value of None, matching the
pre-existing handler contract.
InsertOp
dataclass
¶
Ensure the child view sits at index inside the parent view.
Handlers must treat this as move-aware: if the child is already
attached to the parent at a different position, it is moved rather
than duplicated. index is clamped by handlers to the current
child count.
DestroyOp
dataclass
¶
DestroyOp(tag: int)
Release the native view registered under tag.
The registry drops its tag record and calls the handler's
destroy hook so platform resources (listeners, timers, image
loads) can be released eagerly instead of waiting for GC.
Next steps¶
- See where the callables stripped from these payloads go in Events.
- See how each op is applied to a concrete widget in Native views.
- Read what handlers size themselves against in Platform metrics.
- Read the diffing pass that produces these lists in Reconciliation.