3 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	5792c3b959	Keep the unit level within its bound: the counter test counts 400 not 2000, the deadline test waits 50 ms not 1 s (issue 895) ... Both still prove what they did: the counter test still collides every run and fails when an increment writes without its revision; the deadline test fails when the read after a failed write takes a later deadline than the ask's.	2026-10-21 16:57:31 +02:00
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