SaaSHub helps you find the best software and product alternatives Learn more →
Rules_rust Alternatives
Similar projects and alternatives to rules_rust
-
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.
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
cargo-sweep
A cargo subcommand for cleaning up unused build files generated by Cargo
-
wg-allocators
Home of the Allocators working group: Paving a path for a standard set of allocator traits to be used in collections!
-
bazel-coverage-report-renderer
Haskell rules for Bazel.
-
llvm-project
The LLVM Project is a collection of modular and reusable compiler and toolchain technologies.
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
CppCoreGuidelines
The C++ Core Guidelines are a set of tried-and-true guidelines, rules, and best practices about coding in C++
-
-
-
-
JITWatch
Log analyser / visualiser for Java HotSpot JIT compiler. Inspect inlining decisions, hot methods, bytecode, and assembly. View results in the JavaFX user interface.
-
-
Git
Git Source Code Mirror - This is a publish-only repository but pull requests can be turned into patches to the mailing list via GitGitGadget (https://gitgitgadget.github.io/). Please follow Documentation/SubmittingPatches procedure for any of your improvements.
-
-
-
-
-
-
proc-macro-workshop
Learn to write Rust procedural macros [Rust Latam conference, Montevideo Uruguay, March 2019]
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
rules_rust reviews and mentions
-
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:
-
Rust fact vs. fiction: 5 Insights from Google's Rust journey in 2022
For Bazel we have an import! macro which expands Blaze targets to normal use statements. Like with Soong, Blaze must then make those targets (vendored crates) available to rustc.
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.
-
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.
-
A note from our sponsor - SaaSHub
www.saashub.com | 28 Mar 2024
Stats
bazelbuild/rules_rust is an open source project licensed under Apache License 2.0 which is an OSI approved license.
The primary programming language of rules_rust is Starlark.