summaryrefslogtreecommitdiff
path: root/lib/rites/rite_ef/precedence_ef.ml
diff options
context:
space:
mode:
Diffstat (limited to 'lib/rites/rite_ef/precedence_ef.ml')
-rw-r--r--lib/rites/rite_ef/precedence_ef.ml10
1 files changed, 5 insertions, 5 deletions
diff --git a/lib/rites/rite_ef/precedence_ef.ml b/lib/rites/rite_ef/precedence_ef.ml
index fcd2116..db7e708 100644
--- a/lib/rites/rite_ef/precedence_ef.ml
+++ b/lib/rites/rite_ef/precedence_ef.ml
@@ -685,11 +685,11 @@ let admit ~(observed : Vocab_ef.rank Precedence.candidate)
than rebuilt ones; undocumented for rite authors" -- documented here,
now that this is the function that note was about). Building a fresh
[{ c with ... }] record anywhere below would silently defeat that
- accounting: the dropped candidate would then match nothing in
- [admitted], and {!Precedence.resolve} would count it as dropped a
- SECOND time (once for real, once because its identity no longer
- matches its own admitted copy) without ever raising -- a silent
- double-count, not a crash, which is exactly why this comment exists. *)
+ accounting: the original would then match nothing in [admitted], so the
+ celebration would surface TWICE in the same day -- once in
+ [commemorations] (the rebuilt copy) and once in [omitted] (the original,
+ which nothing admitted matches). One admission, double-reported, and no
+ crash to announce it, which is exactly why this comment exists. *)
let sorted = List.stable_sort compare_dignity comms in
let is_privileged (_, p) = p = Precedence.Privileged in
let observed_rank = observed.Precedence.cel.Celebration.rank in