xflags
By matklad
cargo-xtask
By matklad
xflags | cargo-xtask | |
---|---|---|
6 | 26 | |
75 | 736 | |
- | - | |
7.5 | 3.0 | |
3 days ago | 10 months ago | |
Rust | ||
Apache License 2.0 | - |
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.
xflags
Posts with mentions or reviews of xflags.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-10-11.
-
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.
cargo-xtask
Posts with mentions or reviews of cargo-xtask.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-06-24.
-
🏃♂️ Use task.go for your Go project scripts
💡 Inspired by matklad/cargo-xtask and based on 🏃♂️ Write your Rust project scripts in task.rs from the Rust ecosystem.
-
clap_completion help requested
Using a cargo-xtask task to generate them as a manual step (inlyne currently does this)
- Cargo xtask: extend cargo with custom commands written in Rust
-
Including a cargo command as a dev dependency
As someone else said just is good for that job, or you could implement an xtask helper for these things and setup a suitable development environment with that: https://github.com/matklad/cargo-xtask/
- Cargo xtask: extend stock, stable cargo with custom commands written in Rust
-
Going beyond build.rs: introducing cargo-px
Well tools like cornucopia, prisma-rust-client, protoc-gen-tonic, they don't generate in build.rs, but instead provide either a cli to be called ahead of time, or provide a library that can be called by your own binary (which should generally follow the xtask pattern)
- Hey Rustaceans! Got a question? Ask here (17/2023)!
-
Best way to include a utility command for my crate?
If I understand, this is a tool for when working on the project itself? Akin to a helper script? You could go the cargo install route as already pointed out but there is also the xtask convention.
-
We have getrandom at home
For simple cli apps for internal use, such as cargo-xtasks, I prefer pico_args due to its fast compile times.
-
Rust for Web Development | An Honest Evaluation
For developer-oriented stuff, there's tools like xshell and cargo-xtask. For operator tasks that need to run in a deployed environment, it's not usually a big lift to add CLI subcommands to your binary. It's certainly more boilerplate and inertia than doing stuff in a live REPL, though, and sometimes difficult to recommend for truly one-off situations.