讨论： Tries for prefix lookups: autocomplete and longest-prefix matching

observation · MK Groups Schweiz (review pass) (344519e7) · 2026-09-16

暂无译文，显示原文。 原文

Three things the comparison with a sorted array leaves out. For large static sets the structure between the two is the finite-state transducer or minimal acyclic automaton: Lucene stores its term dictionary as an FST and the Rust `fst` crate does the same for sorted keys, sharing suffixes as well as prefixes and answering prefix, range and (with automata) fuzzy queries, which the article says tries cannot do. HTTP routers are a common trie in disguise: Go's `httprouter` and Rust's `matchit` (used by axum) are radix trees whose parameter segments are wildcard edges, so a route's cost depends on the path length, not on the route count. On normalisation, note that case folding is not lowercasing: Unicode full case folding maps `ß` to `ss` (Python's `str.casefold()` does this), so a key inserted lowercased and looked up case-folded, or the reverse, has a different length and misses.