Use the unified Hashtable API in client-side stats - #12312

Draft

dougqh wants to merge 13 commits into

feat/hashtable-api-unificationfrom

feat/client-side-stats-hashtable-api

Commits on Aug 28, 2026

Carry Maybe<T> forward pending #12328 merge
dougqh
committed
a0629a1
Add Maybe-returning tryGetOrCreateAsMaybe to Hashtable and FlatHashtable
dougqh
committed
effe9ea
Promote tryGetOrCreateAsMaybe to tryGetOrCreate, demote nullable form to tryGetOrCreateOrNull
dougqh
committed
ccf2f1b
Migrate AggregateTable to the blessed Hashtable API

dougqh
and
claude
committed
1d9c2c0
Encapsulate the staleness rule as AggregateEntry.isStale

dougqh
and
claude
committed
ee128fb
Reach State only through the statics in AggregateTable

dougqh
and
claude
committed
6461012
Follow the estimateSize/isLikelyEmpty rename in AggregateTable

dougqh
and
claude
committed
e565370
Rehome the eviction rationale after deleting evictOneStale

dougqh
and
claude
committed
8ad2642
Delete the deprecated Hashtable.Support facade

dougqh
and
claude
committed
b4af2d9
Fuse the CardinalityLimitReporter counter bump into tryGetOrUpdate

dougqh
and
claude
committed
fa402d6
Rewrap an AggregateTable javadoc paragraph per spotless

dougqh
and
claude
committed
7a61535
Fuse CardinalityLimitReporter.record via Maybe, inline the count-bump as a method reference
dougqh
committed
4d41f3f
Inline AggregateEntry::isStale at its call sites, drop the STALE field
dougqh
committed
ab7ec53