On Fri, 18 Sept 2026 at 15:01, Ewan Young <[email protected]> wrote: > v3 looks good to me. The nvalues == 1 restriction on the first-key > MINVALUE/MAXVALUE trim is a clear improvement: the leading single-key > step already trims the default there, and the BTEqualStrategyNumber > block handles the multi-key prefixes, so the intersection removes the > default without repeating the first-key check in every step. Your > comment rewrite explains the interaction much better than my original; > agreed it was too thin. > > Happy with the adjustments -- thanks for picking this up.
OK thanks. I did a bit more work on the tests and pushed. David
