nutype
cargo-xtask
nutype | cargo-xtask | |
---|---|---|
7 | 26 | |
1,209 | 736 | |
- | - | |
8.9 | 5.4 | |
27 days ago | 5 days ago | |
Rust | ||
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.
nutype
- Nutype 0.4.0 released
- Nutype 0.3.0 released
-
Nutype 0.2.0 is released.
The release notes: https://github.com/greyblake/nutype/releases/tag/v0.2.0
-
Rust for Web Development | An Honest Evaluation
Regarding your macro system for "new nominal types" - are you talking about something in the vein of nutype or prae?
-
Nutype: the newtype with guarantees
I need some time to think about this. If you don't mind I pasted your message to a Github discussion , so I don't forget it: https://github.com/greyblake/nutype/discussions/11
cargo-xtask
-
πββοΈ 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.
What are some alternatives?
hado-rs
just - π€ Just a command runner
pad-motion - Implementation of Cemuhook gamepad motion protocol.
cargo-make - Rust task runner and build tool.
r4d - A macro processor made with rust, which aims to be a modern alternative to m4 macro processor.
bors-ng - π A merge bot for GitHub Pull Requests
windows-drivers-rs - Platform that enables Windows driver development in Rust. Developed by Surface.
rust - Empowering everyone to build reliable and efficient software.
enum-code - derive(Code) simplifies error handling by providing an easy-to-use enumeration of error codes
waihona - Rust crate for performing cloud storage CRUD actions across major cloud providers e.g aws
identicon-rs - A simple identicon implementation in rust
fzf - :cherry_blossom: A command-line fuzzy finder