rules_rust
cargo-sweep
Our great sponsors
rules_rust | cargo-sweep | |
---|---|---|
9 | 9 | |
610 | 666 | |
4.1% | - | |
9.6 | 6.6 | |
1 day ago | about 1 month ago | |
Starlark | 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.
rules_rust
-
NixOS: Declarative Builds and Deployments
The same reason Bazel builds avoid using Cargo when building Rust software, so I'll describe why Bazel would do this:
- Bazel wants to cache remote resources, like each respective crate's source files.
- Bazel then wants to build each crate in a sandbox, and cache the build artifacts
This is an established practice, and Nix wants to drive the build for the same reasons.
See:
- https://github.com/bazelbuild/rules_rust
- https://github.com/google/cargo-raze
-
Rust fact vs. fiction: 5 Insights from Google's Rust journey in 2022
To answer your question, I don't know if Soong or Bazel can reuse the files produced by an incremental Rust compilation. I tried searching the rules_rust repository and found some discussions, but nothing that clearly told me "Yes, this is supported".
-
When to Use Bazel?
Bazel doesn't allow targeting a lot of platforms (especially embedded) from Rust, even when the Rust ecosystem supports these targets. Something is off with its design if new work needs to be done for every platform that's already available behind an interface that's as consistent as what rustc gives.
What is supported needs to be inferred from this file, as far as I can tell: https://github.com/bazelbuild/rules_rust/blob/main/rust/plat...
-
Cpp-like build tools for Rust?
You might be overjoyed to learn that you can use a build tool that forces you to manually write out the dependencies between each file.
-
How to enable suggestions/autocomplete in VS Code?
I am using rules_rust and have the VS Code Bazel plugin installed, but I am still not getting autocomplete.
-
Blog Post: Fast Rust Builds
Other than that, the performance of both for builds should be determined exactly by the organization of code into separate crates and the rustc invocations. Bazel generally encourages smaller crates, but that's very subtle. There is at least 1 case I can think of where rustc is overfit to cargo, in a way that is not easily replicable by bazel, which is the metadata/rlib pipelining https://github.com/bazelbuild/rules_rust/issues/228
-
Modern C++ Won't Save Us (2019)
Rust integrates pretty seamlessly into Bazel projects via rules_rust (https://github.com/bazelbuild/rules_rust). The existing rules even allow for c calling rust and rust calling c. Example: https://github.com/bazelbuild/rules_rust/blob/main/examples/...
-
Why Zig When There Is Already C++ and Rust?
With any compiled language you can use the compiler and vendor your dependencies instead of using the language's conventional package manager. For example, nothing prevents skipping Cargo and building Rust directly with rustc the way Bazel does.
https://github.com/bazelbuild/rules_rust
cargo-sweep
-
Target file are very huge and running out of storage on mac.
You can use cargo sweep or kondo to clean up unused files.
-
What are some useful tools for Rust?
cargo-sweep
-
crates.io now has more than 100,000 crates!
[1]: https://github.com/holmgr/cargo-sweep
-
Cargo Clean All - A cargo plugin to clean all your projects at once with filters
I use https://github.com/holmgr/cargo-sweep which can keep files from the current compiler version, but delete files from earlier compilers that won't ever be used again.
-
Announcing cargo-cleanall
How is this different from https://github.com/holmgr/cargo-sweep ?
-
Is this normal? Giant debug folder
I like https://github.com/holmgr/cargo-sweep to keep the size of /target from unbounded growth without fully losing the useful portion of the cache. It's the same outcome as Cargo clean after a reboot but I recently also started using a ramdisk with CARGO_TARGET_DIR. Much easier to do on Linux.
- Cargo clean for a number of projects
-
Blog Post: Fast Rust Builds
cargo-sweep can do this kind of garbage collection along a few axes - rustc version, file age, was or wasn't used during recent build. Works great on Linux. I've not gotten it working reliably for -s/-f on MacOS+APFS, but for the CI use case it should be a nice improvement.
-
STOP DOING RUST
holmgr is a god and cargo-sweep is a godsend
What are some alternatives?
zig - General-purpose programming language and toolchain for maintaining robust, optimal, and reusable software.
cargo-chef - A cargo-subcommand to speed up Rust Docker builds using Docker layer caching.
cargo-clean-all
www.ziglang.org
kondo - Cleans dependencies and build artifacts from your projects.
wg-allocators - Home of the Allocators working group: Paving a path for a standard set of allocator traits to be used in collections!
squatternaut - A snapshot of name squatting on crates.io
bazel-coverage-report-renderer - Haskell rules for Bazel.
cargo-hack - Cargo subcommand to provide various options useful for testing and continuous integration.
llvm-project - The LLVM Project is a collection of modular and reusable compiler and toolchain technologies.
proc-macro2