- How many approaches are there to create a parser?
- When should I use the builder vs derive APIs?
- Why is there a default subcommand of help?
First, let me say that these comparisons are highly subjective, and not meant
in a critical or harsh manner. All the argument parsing libraries out there (to
clap) have their own strengths and weaknesses. Sometimes it just
comes down to personal taste when all other factors are equal. When in doubt,
try them all and pick one that you enjoy :). There’s plenty of room in the Rust
community for multiple implementations!
For less detailed but more broad comparisons, see argparse-benchmarks.
structopt started as a derive API built on
top of clap v2. With clap v3, we’ve forked structopt and integrated it
directly into clap. structopt is in
with the release of
The benefits of integrating
- Easier cross-linking in documentation
- Documentation parity
- Tighter design feedback loop, ensuring all new features are designed with
derives in mind and easier to change
clapin response to
- Clearer endorsement of
clap is as fast, and as lightweight as possible while still giving all the features you’d expect from a modern argument parser. In fact, for the amount and type of features
clap offers it remains about as fast as
getopts. If you use
clap, when you just need some simple arguments parsed, you’ll find it’s a walk in the park.
clap also makes it possible to represent extremely complex and advanced requirements without too much thought.
clap aims to be intuitive, easy to use, and fully capable for wide variety use cases and needs.
Depending on the style in which you choose to define the valid arguments,
clap can be very verbose.
clap also offers so many finetuning knobs and dials, that learning everything can seem overwhelming. I strive to keep the simple cases simple, but when turning all those custom dials it can get complex.
clap is also opinionated about parsing. Even though so much can be tweaked and tuned with
clap (and I’m adding more all the time), there are still certain features which
clap implements in specific ways that may be contrary to some users’ use-cases.
- You want all the nice CLI features your users may expect, yet you don’t want to implement them all yourself. You’d like to focus on your application, not argument parsing.
- In addition to the point above, you don’t want to sacrifice performance to get all those nice features.
- You have complex requirements/conflicts between your various valid args.
- You want to use subcommands (although other libraries also support subcommands, they are not nearly as feature rich as those provided by
- You want some sort of custom validation built into the argument parsing process, instead of as part of your application (which allows for earlier failures, better error messages, more cohesive experience, etc.).
The following APIs are supported:
Previously, we supported:
There are also experiments with other APIs:
Our default answer is to use the Derive API:
- Easier to read, write, and modify
- Easier to keep the argument declaration and reading of argument in sync
- Easier to reuse, e.g. clap-verbosity-flag
The Builder API is a lower-level API that someone might want to use for
- Faster compile times if you aren’t already using other procedural macros
- More flexibility, e.g. you can look up an arguments values, their ordering with other arguments, and what set them. The Derive API can only report values and not indices of or other data.
There is only a default subcommand of
help when other subcommands have been defined manually. So it’s opt-in(ish), being that you only get a
help subcommand if you’re actually using subcommands.
Also, if the user defined a
help subcommand themselves, the auto-generated one wouldn’t be added (meaning it’s only generated if the user hasn’t defined one themselves).