Rust: a record with unread slots is held read-only (slot-readonly-rs) #127
Loading…
Reference in a new issue
No description provided.
Delete branch "hands/slot-readonly-rs"
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:bytes-after-land-and-slot-leaves, speccultlib-gaps:cut_spec:cut-slot-readonly-rs.r1, rulingsslot-mark-consent,slot-unmeasurable-type: cultcache-rs holds a record whose payload carries slots past its reader's declared slots, at any depth, read-only (every write, removal andload_soareplacement refused, store unchanged). Consent follows the union-parity README (Rust has no compatible ids, so every mark is unconsented). Vectors walked:extra-slot-store.cc(minus the variant row, unreadable here),extra-slot-consent.cc,slot-outcomes.msgpack(not grown;outcomes.msgpackstill 9 rows). A held payload this build cannot decode is read-only too.Divergences stated, not hidden: a mesh raw snapshot pull keeps documents applied before a refused one while C# applies one atomic commit (follow-up
mesh-snapshot-atomic); a corrupt held record has no cache-level exit (follow-upread-only-corrupt-record-exit); a written payload carrying slots is judged at the next write.Semver: Unreleased/Breaking in the cultcache-rs CHANGELOG; implies a minor bump while 0.x (0.3.1 to 0.4.0). Touches one line in cultnet-rs
replication.rs.Soul: verdicts
cut-slot-readonly-rs.s1(blocked onload_soalaundering a marked record),.s2(no blockers),.s3. Reports h1 to h3. cultcache-rs, cultnet-rs, cultmesh-rs exit 0; 28 hand mutations killed.🤖 Generated with Claude Code