hexyl

What's broken on a file whose name starts with a digit emits C that does not compile, because a C identifier cannot begin with one: , which #242 asked for parity with, handles it: The cause The sanitizer in maps non-alphanumerics to but never guards the first character, so a leading digit survives. The fix Prefix in that case, matching xxd. After: Names that do not start with a digit are untouched: still gives . One case I deliberately left alone is Unicode-aware, so becomes . That looked wrong to me at first, but gcc accepts it (C99 universal character names in identifiers) and it compiles, so I left it rather than widen the diff. Say the word if you would rather restrict the whole thing to ASCII. Verification is 5 and 41 passing with 0 failures, and are clean. A test alongside the existing covers the digit case. Reverting the guard with the test kept fails it on exactly the identifier. Changelog entry added under a new unreleased section, per CONTRIBUTING. There was no unreleased section yet, so I created one; move it if you would rather it went elsewhere. There is no issue for this, I found it while reading the include-mode code.

Summary Add to the existing cross-compilation matrix, alongside the already supported Linux ARM64 GNU target. Validation The full CI run, including the new target, passed: CICD. The uploaded ARM64-musl binary was inspected after the run and is statically linked.

Summary Add aarch64-pc-windows-msvc to the existing release matrix using the native windows-11-arm runner. Validation The complete workflow passed in my fork, including native Windows ARM64 build, tests, packaging, and artifact upload: https://github.com/meop/hexyl/actions/runs/31940648131 Disclosure This change was prepared with assistance from OpenAI Codex. I reviewed the resulting diff and validated it through the linked GitHub Actions run.