cargo-edit
anyhow
Our great sponsors
cargo-edit | anyhow | |
---|---|---|
45 | 13 | |
2,985 | 5,029 | |
- | - | |
7.4 | 8.4 | |
2 months ago | 10 days ago | |
Rust | Rust | |
MIT License | Apache License 2.0 |
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.
cargo-edit
-
Hey Rustaceans! Got a question? Ask here (23/2023)!
“cargo add” from https://github.com/killercup/cargo-edit has that behavior, but not the built in one that was added to cargo
-
Is Rust's cargo-edit crate still relevant?
I have also noticed that the last commit of cargo-edit crate's GitHub repo (https://github.com/killercup/cargo-edit) was two days ago (pretty recent.) So it is probably relevant for a lot of people.
-
What are some useful tools for Rust?
cargo-upgrade from cargo-edit (somewhat more intentional than builtin update)
-
How to list upgradable crates programmatically
I've also tried cargo-upgrade from cargo-edit like so:
-
Hey Rustaceans! Got a question? Ask here (9/2023)!
You can also see how other crates do it. For example, cargo-edit is just like that - a single package with a library with a couple of small cli wrappers around it. You can compare their Cargo.toml to yours, maybe there is something different about them.
-
`toml` vs `toml_edit` (ie `toml` 0.6 is out)
Just to check, are you aware of cargo-edit's cargo-set-version or cargo-release?
-
Rust 1.66
Speaking of cargo remove, see also cargo-edit [0] from which adding and removing originally came, as well as cargo-binstall [1] which installs binaries rather than compiling from source every time. The binaries are updatable with cargo-update [2].
The latter two can replace a package manager for Rust related utilities, as I often find that those in OS package repositories are often not as up to date as directly from cargo.
[0] https://github.com/killercup/cargo-edit
-
TIL about cargo add
For context, it was/is part of cargo-edit crate which provides other nice functionalities as well. Hope all gets integrated in time.
-
how can I use same crate but with different features?
https://github.com/killercup/cargo-edit can use the F option
- `cargo-set-version` support for workspace inheritance released in cargo-edit 0.11.4!
anyhow
-
I love building a startup in Rust. I wouldn't pick it again.
Depending on your use case, thiserror and/or anyhow.
-
Why Rust?
There is ? as well as the anyhow(https://github.com/dtolnay/anyhow) crate that deals with long nested result chains.
- Anyhow/src/ensure.rs: Rust macro with 675 lines
-
Is this a good way of handling errors in Rust?
There are crates out there that help you reduce this boiler plate. thiserror is good for creating custom errors and color-eyre or anyhow are good for dynamic errors.
-
Looking for general advice on toy project
Give anyhow a look.
-
Oops, I Did It Again...I Made A Rust Web API And It Was Not That Difficult
I've brought anyhow::Result into scope, making error handling super easy to use. We don't need to specify all our Error types. It can automatically convert any errors that implement std::error::Error, which should be all of them. If an error propagates all the way up to main(), we'll get all the info it's captured printed to stdout.
-
Idiomatic way to return/break if Err/None
Alternatively, if you've got a lot of error types and you're outside a library (so directly in a binary where you don't plan to reuse code elsewhere) you can use anyhow. This gives you an error type you can basically propagate any other error through. On top of that you can attach context information at every return. It's basically a more complicated Result>.
-
Using workspace for modularization is kind of painful?
One approach is to define a separate error type for each crate and then use anyhow, eyre or Box to wrap the error, whever a function can return errors originating in several different crates.
-
Can we please stop downvoting people who dislike Rust?
Have you tried anyhow and thiserror for making it as simple as .context("Message") or ? to type-convert and propagate errors up the call stack?
What are some alternatives?
nexus-repository-cargo - Nexus Repository Cargo Format
eyre - A trait object based error handling type for easy idiomatic error handling and reporting in Rust applications
cargo-outdated - A cargo subcommand for displaying when Rust dependencies are out of date
color-eyre - Custom hooks for colorful human oriented error reports via panics and the eyre crate
Cargo - The Rust package manager
thiserror - derive(Error) for struct and enum error types
cargo-do - allows you to run multiple cargo commands in a row
rust - Rust language bindings for TensorFlow
cargo-dot - Generate graphs of a Cargo project's dependencies
structopt - Parse command line arguments by defining a struct.
cargo-script - Cargo script subcommand
hyper - An HTTP library for Rust