eyre
cargo-edit
| eyre | cargo-edit | |
|---|---|---|
| 3 | 45 | |
| 1,191 | 2,988 | |
| 3.5% | - | |
| 8.0 | 7.4 | |
| 6 days ago | 3 months ago | |
| Rust | Rust | |
| Apache License 2.0 | 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.
eyre
- Rust: Enums to Wrap Multiple Errors
-
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.
- Is anybody using `anyhow` with `PyO3`?
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
[1] https://github.com/cargo-bins/cargo-binstall
[2] https://github.com/nabijaczleweli/cargo-update
-
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!
What are some alternatives?
anyhow - Flexible concrete Error type built on std::error::Error
nexus-repository-cargo - Nexus Repository Cargo Format
rust-notes
cargo-outdated - A cargo subcommand for displaying when Rust dependencies are out of date
project-error-handling - Error handling project group
Cargo - The Rust package manager
rfcs - RFCs for changes to Rust
cargo-do - allows you to run multiple cargo commands in a row
cargo-dot - Generate graphs of a Cargo project's dependencies
cargo-script - Cargo script subcommand
cargo-watch - Watches over your Cargo project's source.
cargo-multi - Extends cargo to execute the given command on multiple crates - upstream is at