venial
pico-args
Our great sponsors
venial | pico-args | |
---|---|---|
5 | 11 | |
181 | 548 | |
- | - | |
7.3 | 3.0 | |
about 1 month ago | 6 months ago | |
Rust | Rust | |
MIT License | 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.
venial
-
Improving build times for derive macros by 3x or more
How myn compares to https://github.com/PoignardAzur/venial?
-
Yet another command line argument parser: bpaf 0.5.5
venial is supposed to be a lighter weight alternative to syn that might work. Besides level of maturity, the biggest risk is slowing things down for people already using syn but I think there was a claim that it wasn't noticeable.
- venial 0.4 - A lightweight alternative to syn
- venial 0.2 - A lightweight alternative to syn
- venial 0.1 - A lightweight alternative to syn
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?
darling - A Rust proc-macro attribute parser
lexopt - Minimalist pedantic command line parser
nanoserde - Serialisation library with zero dependencies
xflags
bpaf - Command line parser with applicative interface
command-line-rust - Code for Command-Line Rust (O'Reilly, 2022, ISBN 9781098109417) https://learning.oreilly.com/library/view/command-line-rust/9781098109424/
rustc-dev-guide - A guide to how rustc works and how to contribute to it.
thiserror - derive(Error) for struct and enum error types
argparse-rosetta-rs - Comparing argparse APIs
cli-guidelines - A guide to help you write better command-line programs, taking traditional UNIX principles and updating them for the modern day.
validator - Simple validation for Rust structs
argh - Rust derive-based argument parsing optimized for code size