Module global_arguments 

Git 2.56.0 global-argument boundaries over unchanged operating-system strings. What: Locate Git 2.56.0 command boundaries without reconstructing native arguments. Why: Policy stages need the command index, but Git remains authoritative for option validation and -C semantics.

In TS you’d write (pseudocode):

// Scan argument boundaries; forward the original global prefix to every repository query.

Structs

GlobalLayout

Immutable positions into the caller’s untouched argument vector.

Enums

GlobalOutcome

Which native Git path follows the global prefix.

Functions

command_tokens

What: The command word and the tokens after it, when the arguments name a command. Option<(&OsString, &[OsString])> is “a pair of borrowed views, or nothing”: the word, and the list of everything after it. Why: Every rule that reads a command’s own options needs exactly this split. Taking it from one function means no rule computes an offset of its own, so no rule can read the command word as one of its options by an arithmetic slip.

global_layout

What: Find a command/query/error boundary with one forward scan. Why: Values such as ‘-h’, empty -C paths and non-UTF-8 filenames remain original opaque argument values. Symlink-sensitive -C chaining is not approximated lexically; repository queries forward the complete prefix.