Cargo
cargo-dot
| Cargo | cargo-dot | |
|---|---|---|
| 286 | - | |
| 15,064 | 37 | |
| 1.2% | - | |
| 10.0 | 0.0 | |
| 2 days ago | over 10 years ago | |
| Rust | Rust | |
| Apache License 2.0 | BSD 3-clause "New" or "Revised" 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
-
FMix: пакетный менеджер для Forth
В Elixir есть Mix. В Rust есть Cargo. В Ruby есть Bundler и RubyGems. В Haskell есть Cabal и Stack. В JavaScript есть npm, pnpm и Yarn. В Go есть modules.
-
Learning Rust by Building nginx-discovery: A Beginner's Journey with AI
The Cargo Book
-
Rust the Process
> It may have been nice to expose some reasonable defaults for code coverage measurements too.
Would love built in coverage support but investigation is needed on the design (https://github.com/rust-lang/cargo/issues/13040) and we likely need to redo how we handle doctests (https://blog.rust-lang.org/inside-rust/2025/10/01/this-devel...).
- The Rust Performance Book
-
15 rust tools to level up your Linux terminal
Cargo package manager: https://doc.rust-lang.org/c
-
Rust Cargo: The Backbone of Rust Development
https://www.rust-lang.org/ https://doc.rust-lang.org/cargo/ https://doc.rust-lang.org/cargo/getting-started/installation.html
-
Why We Chose Rust For Spin
cargo, rustfmt, clippy, rust-analyzer, and Rust’s robust unit testing capabilities together form a powerful ecosystem for managing large-scale projects like Spin.
-
Why doesn't Rust care more about compiler performance?
That work is being tracked in https://github.com/rust-lang/cargo/issues/5931
Someone has taken up the work on this though there are some foundational steps first.
1. We need to delineate intermediate and final build artifacts so people have a clearer understanding in `target/` what has stability guarantees (implemented, awaiting stabilization).
2. We then need to re-organize the target directory from being organized by file type to being organized by crate instance.
3. We need to re-do the file locking for `target/` so when we share things, one cargo process won't lock out your entire system
4. We can then start exploring moving intermediate artifacts into a central location.
There are some caveats to this initial implementation
- To avoid cache poisoning, this will only items with immutable source that and an idempotent build, leaving out your local source and stuff that depends on build scripts and proc-macros. There is work to reduce the reliance on build scripts and proc-macros. We may also need a "trust me, this is idempotent" flag for some remaining cases.
- A new instance of a crate will be created in the cache if any dependency changes versions, reducing reuse. This becomes worse when foundation crates release frequently and when adding or updating a specific dependency, Cargo prefers to keep all existing versions, creating a very unpredictable dependency tree. Support for remote caches, especially if you can use your project's CI as a cache source, would help a lot with this.
-
Reducing Cargo target directory size with -Zno-embed-metadata
> It seems wild to consider such intermediate files as part of public API. Someone relying on it does not automatically make it a breaking change if it’s not documented.
To find what is considered an intermediate vs a final artifact from cargo, you need to check out https://doc.rust-lang.org/cargo/reference/build-cache.html
We are working on making this clearer with https://github.com/rust-lang/cargo/issues/14125 where there will be `build.build-dir` (intermediate files) and `build.target-dir` (final artifacts).
When you do a `cargo build` inside of a library, like `clap`, you will get an rlip copied into `build.target-dir` (final artifacts). This is intended for integration with other build systems. There are holes with this workflow though but identifying all of the relevant cases for what might be a "safe" breakage is difficult.
-
Malware found on NPM infecting local package with reverse shell
See https://github.com/rust-lang/cargo/issues/13897 and https://github.com/rust-lang/cargo/issues/13897#issuecomment... .
cargo-dot
We haven't tracked posts mentioning cargo-dot yet.
Tracking mentions began in Dec 2020.
What are some alternatives?
overflower - A Rust compiler plugin and support library to annotate overflow behavior
cargo-edit - A utility for managing cargo dependencies from the command line.
cargo-check
cargo-count - a cargo subcommand for counting lines of code in Rust projects
RustCMake - An example project showing usage of CMake with Rust
cargo-graph