A borrowed slice, buffered reader, and memory map can all feed the same Rust scanner, but they move and own bytes differently. I trace each boundary and its trade-offs.
Zero-copy scanning still reads every inspected byte. It removes a second materialization in memory. I use streaming Aho-Corasick to explain automaton state, chunk boundaries, DFA dependency chains, prefilters, and honest performance measurement.