Slot tolerance: a record with unread slots is held read-only, not shed #124
Loading…
Reference in a new issue
No description provided.
Delete branch "hands/slot-tolerance"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
cultlib-gaps:follow_up:slot-tolerance-r4-land, speccultlib-gaps:cut_spec:cut-slot-tolerance.r5: a record whose payload carries slots past its reader's declared slots, at any depth, is held read-only (every write or removal refused, nothing changed on disk) instead of shedding the slots on the next write; consent followscultlib-gaps:ruling:slot-mark-consent; types the guard cannot measure are not guarded (cultlib-gaps:ruling:slot-unmeasurable-type). Vectors intests/vectors/union-parity/(extra-slot-store, extra-slot-consent, slot-outcomes) for the TS, Python and Rust leaf cuts (cut-slot-readonly-{ts,py,rs}).Semver: Breaking in
unity/org.gamecult.cultlib/CHANGELOG.md(writes that used to succeed are refused). ApiCompat (measureApiBreaksagainst cultlib-unity-v3.0.0): 0 breaks; public additions only.Soul: verdicts
cut-slot-tolerance.s1to.s4(s1 to s3 blocked on false read-only marks, Flatten through a marked base, the formatter-identity decision and a stale GeneratorConsumer check; s4 held). Caching 1347, Mesh 357, Networking 830 passed, GeneratorConsumer exit 0, vectors regenerate byte-identical.🤖 Generated with Claude Code
e41e99e0dc44c798d583