Go-Style vs. GNU-Style Flag Parsing

WHY IT EXISTS: Command-line tools need a way to interpret user input like -v or --user=admin. While most Unix-like systems follow the POSIX/GNU conventions for this, Google's Go language introduced its own, simpler flag package. This created a different "dialect" of command-line parsing that developers and users need to be aware of.

THE MENTAL MODEL: Imagine two ways of giving instructions. The POSIX/GNU way is a flexible conversation where you can add details (--verbose) at any point. The Go flag way is like filling out a form: you list all your options (-lines=10 -force) at the top, and once you start listing the main items (positional arguments), you can't go back and add more options.

HOW IT WORKS: Go's flag package, and Rust's go-flag compatibility crate, differ from the GNU standard in three key ways. First, there is no concept of separate short and long flags; -f and --f are the same, and there's no automatic pairing like -f with --force. Second, combining short flags is not supported; -fd is parsed as a single flag named "fd", not as flags "f" and "d". Third, flag parsing stops as soon as the first non-flag argument is encountered. Any subsequent items, even if they look like flags, are treated as positional arguments.

WHEN TO USE IT: Use a Go-style parser, like Rust's go-flag crate, when you are porting a command-line application from Go to Rust. This ensures that existing users and scripts that rely on the tool's specific command-line behavior won't break. It provides a stable transition path before potentially migrating to a more idiomatic, feature-rich Rust parser like clap.

WHEN NOT TO USE IT: Avoid Go-style parsing when writing a new CLI tool from scratch in Rust or another language. Modern users generally expect the flexibility of POSIX/GNU conventions (short/long flags, combined flags, flags after args). Using a standard library like clap in Rust will provide a better user experience and more features, such as subcommands, which are out of scope for Go's flag package.

ONE CANONICAL EXAMPLE: A Go program defines two flags: force (boolean) and lines (integer). A user runs ./my-tool -lines=20 file.txt -force. With Go-style parsing, lines is set to 20, but -force is treated as a second positional argument alongside file.txt because it appears after the first argument. With GNU-style parsing, both flags would be correctly parsed.