Aho–Corasick: Mental Model

Start with the idea

Begin with the concrete question: Return matched pattern count including overlaps. For the visible input text=ahishers patterns=[he,she,his,hers], the stated result is 4. Before reading code, name the smallest piece of information that must survive from one step to the next. String algorithms compare symbols or prefixes, but a Rust String is UTF-8 bytes. State whether the task means bytes, scalar values, or grapheme clusters. That is the mental model for Aho–Corasick; it gives you a reason for each update instead of a line of code to memorise.

The core mechanism is this: Add failure links to a trie so one scan reports all pattern suffixes ending at each position. Treat it as a claim to test after every operation. Write down the state before the first operation, update it once, and ask which part of the claim is still true. If an item is skipped, inserted, or removed, explain why that action cannot destroy an answer that should be retained. A useful trace has columns for the current input position, the state before the step, the action, and the state afterward. Use the visible sample until the expected result becomes inevitable rather than merely plausible.

Now inspect the Rust sketch, not just its final expression. The supplied Rust sketch is a starting point. Identify what it stores, how one iteration changes it, and whether it already solves the exact task or only demonstrates a related operation. Use bytes only when the input contract permits byte-wise matching.