RangeStat
Tracks the minimum and maximum value seen across a stream.
Use cases: observed range / spread monitoring; pairs with quantile stats to confirm coverage of the range under observation.
Memory: O(1); two double cells.
Update: O(1) per observation (one CAS-min + one CAS-max).
Concurrency: Two independent CAS-min/CAS-max cells; each exact under every Concurrency level. A read() between the two CAS writes of a single update can briefly observe min > max on a never-yet-updated stat under heavy contention, but the per-cell guarantees hold.
Constructors
RangeStat
Properties
concurrency
Thread-safety mode fixed at construction. See Concurrency for the shared contract and the implementation's KDoc for its cell and lock strategy.
Functions
create
Create an independent accumulator at the configured baseline. A null concurrency preserves this accumulator's mode; a non-null value overrides it. Modality subtypes narrow the return type to preserve the input shape.
merge
Fold a compatible snapshot values into this accumulator at timestampNanos. Implementations document whether the combine is exact or approximate and which state the snapshot omits. The source accumulator is unaffected.
Time-dependent statistics, such as windows, place the snapshot at timestampNanos, which must share the clock the caller uses for updates and reads. Time-independent statistics ignore it.
read
Return the current result evaluated at timestampNanos. Time-independent statistics ignore the timestamp. Reading does not add an observation.
Snapshot consistency depends on the implementation's synchronisation. Locks protect coupled state under Concurrency.Strict and Concurrency.HighWrite; independently updated cells and JVM striped adders can still yield a best-effort snapshot. Concurrency.Relaxed permits drift across coupled cells.
reset
Restore the configured baseline, including any prior seed. Preserves the configuration and concurrency.