Skip to content

Commit 583c221

Browse files
luisleo526claude
andcommitted
CR-150 WL-PTAILFIX: reword one comment that named a nonexistent identifier (source-guard-dangling-comment-names)
The first lab preflight of the fix (rj-20261020t214222-94a2b7) failed the dangling-comment-names stage on include/pineforge/detail/id_pair_ordered_fold.hpp:50, where a comment spelled 2^(off_t_bits-6) although no identifier off_t_bits exists. The verifier-tests failures of the same job were the same finding leaking into test_ci_verify's expected stage lists. The comment now says "2^(B-6) slots, where B is the number of value bits of off_t". No code change. Co-Authored-By: Claude Sonnet 5.5 <[email protected]>
1 parent 4d6cd2b commit 583c221

1 file changed

Lines changed: 3 additions & 2 deletions

File tree

‎include/pineforge/detail/id_pair_ordered_fold.hpp‎

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -47,8 +47,9 @@ class BrokerStateByteFold {
4747
static_assert(sizeof(BrokerStateByteFold) == 2056, "exact fold has 257 words");
4848

4949
// A map file must not impose a lower key-count ceiling than the existing
50-
// hash index. Its largest power-of-two slot array has 2^(off_t_bits-6)
51-
// slots, at half load: at most (OFF_MAX/64)+1 distinct rows. Segment large
50+
// hash index. Its largest power-of-two slot array has 2^(B-6) slots, where B
51+
// is the number of value bits of off_t, at half load: at most (OFF_MAX/64)+1
52+
// distinct rows. Segment large
5253
// records across a FIXED descriptor array covering that entire population.
5354
// Normal runs open just one segment of each file. No resident directory
5455
// grows with keys; no fold-specific capacity/exhaustion error is introduced.

0 commit comments

Comments
 (0)