From 90ad9e632520d3bbc22562c0fd4db2584ef2a92c Mon Sep 17 00:00:00 2001 From: tv Date: Sun, 15 Nov 2026 16:49:08 +0000 Subject: store: a signed value chosen by seq is named so Where the policy asks for signed values, a place's value is chosen by `seq`, but conflict reports still called the choice `newestWins`, and the code and the architecture still said "newest" of what a read shows. A report names it `highestSeq`; the rest says "the one a read shows". --- src/document/store.rs | 18 +++++++++++++----- 1 file changed, 13 insertions(+), 5 deletions(-) (limited to 'src') diff --git a/src/document/store.rs b/src/document/store.rs index 9afb5d3..bc50535 100644 --- a/src/document/store.rs +++ b/src/document/store.rs @@ -206,7 +206,7 @@ fn op_order(id: &ObjId) -> (u64, Option<&ActorId>) { enum Resolved { /// Concurrent maps presented as one. Newest first; `[0]` is canonical for writes. Maps(Vec), - /// Any other value: the newest concurrent candidate. + /// Any other value: the concurrent candidate a read shows (`candidates`). Other(Value<'static>, ObjId), } @@ -1222,8 +1222,7 @@ fn parent_for_write(doc: &mut impl Transactable, parents: &[String]) -> Result

Result Result