getargs
A truly zero-cost argument parser for Rust (by j-tai)
lexopt
Minimalist pedantic command line parser (by blyxxyz)
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
getargs
Posts with mentions or reviews of getargs.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-10-08.
-
Announcement: xflags 3.0.0
Actually, I would say getargs on this one. Full disclosure, I'm a major contributor to the library, but it is also faster than lexopt, and provides a bit more control.
-
Inlining functions that will only ever be called once - is this a good convention?
I have benchmarked getargs to have significant performance gains from inlining.
-
How do i learn about new crates?
I'd recommend getargs over argparse, it's also very well documented (but that version is not on crates.io yet)
-
How to parse `strace -c ls -a` using clap?
It pains me that getargs 0.5.0 is still not released yet. If you can deal with a git dependency, I would highly recommend it, it can do exactly what you want with no fuss.
-
What's everyone working on this week (23/2022)?
I'm currently working on bringing up getargs, which was abandoned on crates.io over 2 years ago. It has an API design that I agree with and I wanted to make it great, so I'm giving it a visit from the PR fairy.
-
What are legitimate problems with Rust?
If it's perfectly fine then it shouldn't be terribly difficult to write it in a way that the borrow checker is happy with. The problem is reformulating your problem such that it's easy to either annotate the lifetimes in that way or have the compiler infer them for you. And it's made more difficult if your libraries have incorrectly elided lifetimes.
lexopt
Posts with mentions or reviews of lexopt.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-10-08.
-
Announcement: xflags 3.0.0
if you want to be maximally minimal, need only basic features (eg, no help generation), and want to be pedantically correct, use lexopt
-
Creating an Argparse library [feedback would be appreciated]
You might also want to check out pico-args, Gumdrop, and lexopt to see if any of them meet your needs.
- lexopt: a minimalist pedantic argument parser
What are some alternatives?
When comparing getargs and lexopt you can also consider the following projects:
faketty - Wrapper to exec a command in a pty, even if redirecting the output
pico-args - An ultra simple CLI arguments parser.
async-fundamentals-initiative
xflags
argi - Argument parsing for the future 🚀
clap-rs - A full featured, fast Command Line Argument Parser for Rust
ripgrep - ripgrep recursively searches directories for a regex pattern while respecting your gitignore
ponyc - Pony is an open-source, actor-model, capabilities-secure, high performance programming language
cargo-supply-chain - Gather author, contributor and publisher data on crates in your dependency graph.
strop - Stochastically generates machine code