ben-manes / caffeine / #5656

100%

master: 100%

push

github

Pin and document the absent-key refresh side-load model

A sync refresh(k) on an absent key registers the reload only in
refreshes() — invisible to a concurrent get, which loads again — while
the async view inserts a first-class in-flight entry a get can join.
This sync/async divergence is structurally forced (a sync cache cannot
join an invisible in-progress computeIfAbsent) and intentional; document
it (A2-F1a) and pin the dup-load with a latch-gated test: sync loads
twice, async once. No user-facing javadoc change.

Also add a discardRefresh-across-the-compute-family reference table to
design-decisions, consolidating the per-verdict rules just verified
consistent across both siblings.

4187 of 4194 branches covered (99.83%)

8439 of 8439 relevant lines covered (100.0%)

1.0 hits per line