Record what the LTO mismatch cost and why the existing function-count check
does not catch it, and add measured per-utility gains to the performance page.
The page promised a report at a terminal without saying that one is only
drawn when the error can be tied to an argument: an error about no single
argument, or an operand rewritten before it could be located, still falls
back to the plain one-line message. Record that, and that a usage error
keeps its "Try --help" hint under the report.
Handle cut's short-only -F mode explicitly and preserve head's original
argv before obsolete option rewriting. Add regression coverage and document
-F among the supported cut modes.
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
The summary already listed this page, but the page itself lived on a
branch of its own, so the link went nowhere. Bring it here, next to the
code it describes, and bring it up to date: env, cut, head, tail and
truncate have carets now, the three shared parsers each explain their
own syntax for every utility that uses them, and a caret can point
inside an argument that had to be echoed back quoted.
* docs: fix macOS tier 1 targets and platform compatibility table
- Add aarch64-apple-darwin to the tier 1 macOS target list.
- Use feat_os_unix for macOS in uudoc.rs, since feat_os_macos does not
exist and caused the compatibility table to show almost no macOS
support.
* uudoc: remove unnecessary comment about macOS feature
* uudoc: drop macos feature entry and use unix for macOS
Some distributions have already adopted uutils as `/bin/ls`. Continuing
to compare against the binary at that path would only result in
comparing against a much older uutils version and fail to compare
against GNU Coreutils at all. Ubuntu 25.10 has prefixed GNU's binaries
with "gnu", so mention this to retain the intended behavior.
xtqqczze