gpui-entity

Manage shared reactive state across GPUI components by creating entities with cx.new and using read, read_with, and update closures. This coordinates synchronized updates and prevents unsafe access patterns in complex UIs.

Prevent memory leaks in GPUI async closures by calling downgrade() to create a WeakEntity<T>. This avoids retain cycles, and you can safely upgrade it later to interact with the state during async tasks spawned via cx.spawn.

Trigger UI updates when mutating GPUI entity state by calling update(cx, |state, cx| ...) to modify the data, followed by cx.notify() inside the closure. This ensures the reactive system registers the changes and re-renders appropriately.

Use read_with(cx, |state, cx| ...) instead of read(cx) when you need to access both the immutable state and the context simultaneously to return a computed value. Use read for simple, direct immutable access to the state.

GPUI automatically disposes of entity state when all strong references to that entity are dropped. This lifecycle management prevents stale state persistence and ensures resources are freed when components are unmounted.