go: a counter by compare-and-set, so a number is handed out once (hq research 042) #16

Merged

mesh-admin merged 2 commits from feat/a-counter-by-compare-and-set into main 2026-10-10 10:37:11 +00:00

Conversation 3 Commits 2 Files Changed 3

+328

2 Commits

Author	SHA1	Message	Date
jochen	9c548753b8	go: say an Increment error other than a lost write may have spent its number, refuse null, and prove the writers collided ... The review of 2026-10-10: a timeout can come after the write landed, so a caller tolerates gaps; a null value is no counter; and a contention test where no write was lost would prove nothing.	2026-10-10 12:33:41 +02:00
jochen	c58ce2c7fe	go: a counter by compare-and-set, so a number is handed out once (hq research 042) ... The coming issues module hands out issue numbers from its own state; two instances must never hand out one number twice. Create and Update already write by compare-and-set (ADR 0259), so State(...).Increment reads, writes one more at the revision read, and on a lost write reads and tries again, bounded by the caller's attempts. A lost write past the bound is ErrChanged, any other refusal and a value that is no counter are returned at once: nothing is reported counted that was not written. Part of the issue tracker decision, hq research 042.	2026-10-10 12:31:05 +02:00