State history: aliasing for duplicate ids + follow-ups (PR #1) #2

New issue

Open

opened 2026-10-12 03:04:56 +00:00 by orchestrator · 0 comments

orchestrator commented

2026-10-12 03:04:56 +00:00

Member

Open decision (needs the lead)

Should a same id across kinds (field(0,'x') vs collection([],'x')) be an error? (orchestrator's question back to the lead on PR #1.)

Implement

Aliasing: same id ⇒ same underlying state; a === b if cheap. Requires resolving an id at construction time, i.e. a registry of all constructed authoritative cells (not the current live-only registry), plus reclamation (constructed-but-never-retained; GC on __dead). Pressure-test this before implementing.

Agreed small follow-ups

Adopt the rewritten module header (minus "SPIKE").
Add an inline comment explaining the read-after-flush.
cid-102 cast cleanup.

Refs

gooey PR #1 (comments 103, 107) + its resume notes.

## Open decision (needs the lead) Should a same id **across kinds** (`field(0,'x')` vs `collection([],'x')`) be an **error**? (orchestrator's question back to the lead on PR #1.) ## Implement **Aliasing**: same id ⇒ same underlying state; `a === b` if cheap. Requires resolving an id at **construction** time, i.e. a registry of all *constructed* authoritative cells (not the current live-only registry), plus reclamation (constructed-but-never-retained; GC on `__dead`). Pressure-test this before implementing. ## Agreed small follow-ups - Adopt the rewritten module header (minus "SPIKE"). - Add an inline comment explaining the read-after-flush. - cid-102 cast cleanup. ## Refs gooey PR #1 (comments 103, 107) + its resume notes.

No labels

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

legend/gooey#2

No description provided.

Rows
Columns