SIMD Parser Utility (Not the Active Parser)
A SIMD utility exists; it is not the active terminal parser.
Availability
The advertised workflow is not available as a connected feature in stable v0.5.1. Source components or future work do not make it a shipped capability.
Reviewed against stable v0.5.1. Rust candidate additions are labeled separately. Release status.
The pain this solves
- Performance descriptions should identify the parser path actually used.
- A standalone helper should not be presented as the active parser.
What ships with it
- Stable source contains a Swift SIMD16 byte-scanning utility.
- Active ANSI parsing uses Rust first with a Swift fallback.
- No production caller of the SIMD utility was found.
Questions this answers
- Does the active terminal parser use SIMD?
- Is the SIMD scanner written in Rust?
- What parser path is active in stable Chau7?
How it works
The stable Swift source defines SIMD16 byte scanning for selected control and printable-byte patterns. This is a Swift utility, not a Rust SIMD parser.
The active ANSI parsing path tries the Rust ANSI parser and falls back to Swift parsing. A static source search found no production caller of the standalone SIMD utility.
Do not describe stable Chau7 as parsing all terminal output with SIMD or as using Rust SIMD. The helper alone does not establish a measured improvement or active integration.
Why it matters
Users should know which code processes terminal output. This distinguishes an available helper from the parser path used by the application.
Frequently asked questions
Is terminal parsing performed by SIMD in stable Chau7?
The active path calls the Rust ANSI parser first and has a Swift fallback. The standalone Swift SIMD utility was not found on that path.
Is this Rust SIMD?
No. The helper is written in Swift and uses Swift SIMD types.