Function read_to_is_inclusive
pub async fn read_to_is_inclusive<F: Fixture>(
open: impl AsyncFn() -> F,
) -> RuleOutcomeExpand description
ReadOptions::to includes the event at that position.
ES-16 and VT-29. The upper bound is inclusive, and both wrong
implementations ES-16’s Rejects: names are here: an adapter that accepts
ReadOptions by value, matches the fields it knows and ignores the rest —
ToBoundIgnoredStore, which returns the whole log and turns a bounded
backfill into an unbounded one with no error anywhere — and an adapter
that reads to as exclusive — ToIsExclusiveStore, which yields a window
one event short at every chunk boundary and is invisible until the chunks
are reassembled.
The events are tagged and their types ascend, and neither is
decoration. Untagged events would let InnerJoinTagStore fail this rule
for a reason untagged_events_match_query_all already owns; descending
types would let SortByEventTypeStore fail it for a reason
read_defaults_to_ascending_order already owns. Neither would be
coverage; both would be inflation.
The assertion names two specific events the store assigned, so a store returning nothing fails it. That is the non-vacuity anchor, and it is why there is no separate one.