How zero-allocation hot paths work in polyfill-rs
mainThe library is designed for high performance by minimizing heap traffic in critical paths.
Zero-allocation coverage: Strict zero-allocation claims apply to tested, warmed hot paths, specifically:
- Existing-level book updates
- Selected read-side calculations
Paths that DO touch the allocator: Certain operations are designed to use the allocator when necessary:
- First time seeing a token/book (HashMap insert + key clone)
- New price levels when a sorted side needs to grow
- Book removal/drop paths that release owned buffers