commit 280df8abb83452f56f340e5b10e358210dfe2904
parent e13bae8f4a7ef5c918f1a38071281b1653a736ff
Author: Jared Tobin <jared@jtobin.io>
Date: Thu, 2 Jul 2026 17:23:08 -0230
docs: README example and CHANGELOG for the log-wealth split
The README GHCi session now shows both accessors at s10 (current
0.6187772969384595 vs supremum 0.916290731874155) and uses
log_wealth_sup for the rejection at s300. CHANGELOG gains an
unreleased entry noting the breaking rename.
Diffstat:
2 files changed, 14 insertions(+), 3 deletions(-)
diff --git a/CHANGELOG b/CHANGELOG
@@ -1,5 +1,14 @@
# Changelog
+- unreleased
+ * 'log_wealth' now returns the current log-wealth, and the
+ supremum-so-far statistic that 'decide' monitors is exposed
+ separately as 'log_wealth_sup'. Applies uniformly across
+ 'Bounded', 'Paired', 'Bernoulli', and 'Bernoulli.TwoSided'.
+
+ Breaking: callers that relied on 'log_wealth' returning the
+ supremum should switch to 'log_wealth_sup'.
+
- 0.2.2 (2026-07-02)
* Adds a Numeric.Eproc.Bernoulli.TwoSided module for a two-sided
Bernoulli rate test.
diff --git a/README.md b/README.md
@@ -25,16 +25,18 @@ A sample GHCi session:
> let xs = [1, 1, 0, 1, 1, 0, 1, 1, 1, 1]
> let s10 = foldl' (Bounded.update cfg) s0 xs
>
- > -- inspect (supremum-so-far) log-wealth and stopping decision at any
- > -- point
+ > -- inspect current and supremum-so-far log-wealth, and the stopping
+ > -- decision, at any point
> Bounded.log_wealth s10
+ 0.6187772969384595
+ > Bounded.log_wealth_sup s10
0.916290731874155
> Bounded.decide cfg s10
Continue
>
> -- with enough evidence, the hypothesis is rejected
> let s300 = foldl' (Bounded.update cfg) s0 (concat (replicate 30 xs))
- > Bounded.log_wealth s300
+ > Bounded.log_wealth_sup s300
51.14271142862292
> Bounded.decide cfg s300
Reject