Cargo
cargo-count
Our great sponsors
| Cargo | cargo-count | |
|---|---|---|
| 122 | 0 | |
| 8,342 | 122 | |
| 3.3% | - | |
| 9.8 | 0.0 | |
| 8 days ago | over 1 year ago | |
| Rust | Rust | |
| GNU General Public License v3.0 or later | 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.
Cargo
-
Announcing Rust 1.61.0
Anybody knows when cargo-add will be distributed in stable cargo? Seems merged already.
I also just noticed a bug, which I reported here.
I created a feature request for the first thing.
-
Nix & Rust - cargo2nix 0.11.0 released
In this case the libary is cargo
- Cargo - The Rust package manager
-
Supply Chain Thoughts
We might not need to reserve all typos. Soon cargo add will be in the stable release and we are hoping to have crates.io start suggesting it along with or in place of the Cargo.toml snippet. cargo-add could check for typos when you add a dependency. We could even check for registry squatting. If all else fails, we can check for security advisories when adding a crate.
-
Understanding the bin, sbin, usr/bin, usr/sbin split (2010)
There is no specific reason for a program that uses the XDG dirs on other unices to not use them on macOS, other than some idea that it's "alien".
You can have ~/.config/. Nothing in macOS prevents you from having it. And so, some programs do. The worst thing that happens is that, instead of having one directoy ~/.foo you now have one directory ~/.config/foo and nothing else in ~/.config. But as soon as you add the second thing that uses ~/.config, you now have two directories in there instead of a second dotdirectory in ~.
It's just that for a bunch of them the XDG path is only used if it exists - e.g. emacs predates the spec, so it uses ~/.emacs.d (and a few others) first.
Cargo doesn't use the XDG paths at all, apparently - https://github.com/rust-lang/cargo/issues/1734. However it also needs a directory for binaries (~/.cargo/bin) and ~/.local/bin isn't actually in the spec at the moment (https://gitlab.freedesktop.org/xdg/xdg-specs/-/issues/14).
-
my first nontrivial rust program compiled!
Can I suggest using rustup (https://rustup.rs/) to manage the rust tool chain and cargo (installed by rustup, but https://github.com/rust-lang/cargo) to manage builds and packages? It makes it much easier to handle projects especially with dependencies. The book (https://doc.rust-lang.org/stable/book/title-page.html) outlines how to use it and some stuff for advancing with rust
-
Hey Rustaceans! Got a question? Ask here! (18/2022)!
The package in question was updated to v3.0 three weeks ago, at the same time as heron itself. Even when I explicitly define the dependency pointing at the git repo (which should find the package subdirectory):
-
Make `cargo doc` exit non-zero if there's warnings
I believe this is the relevant tracking issue
cargo-count
We haven't tracked posts mentioning cargo-count yet.
Tracking mentions began in Dec 2020.
What are some alternatives?
RustCMake - An example project showing usage of CMake with Rust
Clippy - A bunch of lints to catch common mistakes and improve your Rust code
cargo-outdated - A cargo subcommand for displaying when Rust dependencies are out of date
crates.io - Source code for crates.io
opencv-rust - Rust bindings for OpenCV 3 & 4
RustScan - 🤖 The Modern Port Scanner 🤖
cargo-check
rust-analyzer - A Rust compiler front-end for IDEs [Moved to: https://github.com/rust-lang/rust-analyzer]
rust-windows-dll - Macro for dynamically loading windows dll functions
windows-rs - Rust for Windows
cargo-edit - A utility for managing cargo dependencies from the command line.
cargo-dot - Generate graphs of a Cargo project's dependencies