xflags | pico-args | |
---|---|---|
6 | 11 | |
75 | 547 | |
- | - | |
7.5 | 3.0 | |
3 days ago | 7 months ago | |
Rust | Rust | |
Apache License 2.0 | MIT License |
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.
xflags
-
Started using Rust for scripting
3) xflags is my preferred way to parse CLI arguments for such scripts. It's not good at all, but, for me, it's the best for the task at the moment.
- Announcement: xflags 3.0.0
-
pico-args: An ultra simple CLI arguments parser with 0 dependencies
You might like xflags. It has a similar design philosophy, but is willing to compromise on simplicity a bit to get auto-generated help.
-
Announcement: xflags, fast-to-compile proc macro for cli args
See also https://github.com/matklad/xflags/issues/3
-
Argument parsers that don't choke on invalid unicode
Added https://github.com/matklad/xflags/blob/master/examples/non-utf8.rs.
pico-args
- Improving build times for derive macros by 3x or more
-
Need a new args parser
That's because the maintainer does not consider it an issue but an implementation detail: https://github.com/RazrFalcon/pico-args/issues/15
-
An alternative to clap but with a stable API?
Maybe pico-args then?
-
Immediately off the top of your head what is the best Rust CLI library.
If I forget to get around to it, would you mind poking RazrFalcon/pico-args about adding it to the comparison chart? I really like using that thing as something I can link people to with just a quick explanation of that particular trade-off.
-
Best CLI arg parser for use in Rust to port from Perl with Getopt::Long?
If fewer dependencies is better, you can't get much fewer than pico-args, which has zero dependencies.
- What is the current proper way to get command line args ?
-
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.
-
Can we please stop downvoting people who dislike Rust?
For example, The Rust compiler isn't slow; we are. and pico-args: Alternatives.
- pico-args: An ultra simple CLI arguments parser with 0 dependencies
-
New:`cargo-fuzzcheck` 0.5.0 and a series of decent, fast-to-compile crates to replace `syn`, `quote`, `serde-json`, and `toml-rs`
For example, I'd love to go from StructOpt to Gumdrop for parsing command-line arguments and cut my compile times and output size by an order of magnitude, but Gumdrop uses String internally, which means it'll panic if it encounters a Windows path with un-paired surrogates or a mojibake'd posix path... some of which I actually have.
What are some alternatives?
argh - Rust derive-based argument parsing optimized for code size
lexopt - Minimalist pedantic command line parser
getargs - A truly zero-cost argument parser for Rust
command-line-rust - Code for Command-Line Rust (O'Reilly, 2022, ISBN 9781098109417) https://learning.oreilly.com/library/view/command-line-rust/9781098109424/
thiserror - derive(Error) for struct and enum error types
gumdrop - Rust option parser with custom derive support
cli-guidelines - A guide to help you write better command-line programs, taking traditional UNIX principles and updating them for the modern day.
clap-rs - A full featured, fast Command Line Argument Parser for Rust
rust - Rust for the xtensa architecture. Built in targets for the ESP32 and ESP8266
auto-fuzz-test - Effortlessly fuzz libraries with large API surfaces