prae
prae is a crate that aims to provide a better way to define types that require validation. (by teenjuna)
cargo-xtask
By matklad
Our great sponsors
| prae | cargo-xtask | |
|---|---|---|
| 6 | 26 | |
| 129 | 736 | |
| - | - | |
| 0.0 | 3.0 | |
| about 1 year ago | 10 months ago | |
| Rust | ||
| The Unlicense | - |
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.
prae
Posts with mentions or reviews of prae.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-02-27.
-
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
Hey! I can't help but notice that this crate is way to similar to my crate prae. Did you see it? You even provide a similar example in the readme...
-
Patterns with Rust types
Since we’re talking about this topic, I want to shamelessly link my crate here: prae
-
New Tokio blog post: Announcing Axum - Web framework that focuses on ergonomics and modularity
Something like this should work pretty well, since it integrates with serde: https://github.com/teenjuna/prae
-
Help fight this conflicting implementation
Seems like .into_inner() would be a better choice. If you interested in the code, take a look! Linking related PR https://github.com/teenjuna/prae/pull/15
-
prae: a simple library that helps you keep your types valid
Meet prae. It provides a simple proc macro that allows you to do small things like this:
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.
What are some alternatives?
When comparing prae and cargo-xtask you can also consider the following projects:
dropshot - expose REST APIs from a Rust program
just - 🤖 Just a command runner
silicon - Create beautiful image of your source code.
cargo-make - Rust task runner and build tool.
syn - Parser for Rust source code
bors-ng - 👁 A merge bot for GitHub Pull Requests
warp - A super-easy, composable, web server framework for warp speeds.
rust - Empowering everyone to build reliable and efficient software.
routerify - A lightweight, idiomatic, composable and modular router implementation with middleware support for the Rust HTTP library hyper.rs
waihona - Rust crate for performing cloud storage CRUD actions across major cloud providers e.g aws
rust-web-framework-comparison - A comparison of some web frameworks and libs written in Rust
fzf - :cherry_blossom: A command-line fuzzy finder