Skip to main content

Module spill

Module spill 

Source
Expand description

Rung 3 of the ladder: spool a non-seekable input so it becomes seekable.

Spilling costs disk and latency, never accuracy — which is why crate::Rung::Spilled counts as authoritative.

Structs§

SpillSource
A seekable source produced by draining a forward-only one.
SpillWriter
The push side of the spill loop: bytes handed over one slice at a time, held in memory up to the policy’s memory cap, then in a temp file, and refused past its hard limit. The one owner of those limits — SpillSource::materialize_from drives it from a reader, and a caller that sees the bytes go past on their way somewhere else (a tee) pushes them itself.

Enums§

SpillPolicy

Constants§

DEFAULT_MAX_SPILL
DEFAULT_MEM_CAP