commit | 78dc893592c048083fdc4e651d31dbdf1f110560 | [log] [tgz] |
---|---|---|
author | Googler <jhorvitz@google.com> | Mon Mar 13 20:09:39 2023 -0700 |
committer | Copybara-Service <copybara-worker@google.com> | Mon Mar 13 20:11:10 2023 -0700 |
tree | 81794063012638a91bbba376ff8f0ca920b3963c | |
parent | 45edbd576e9230c5f195a67deaf3ae35a7319a05 [diff] |
Inline `AttributeContainer` into `Rule`. There is a one-to-one relationship between these two classes. Combining them saves memory by cutting out the per-object cost. `Rule` has a net change of +1 field which offsets some of the benefit, but I plan on optimizing `Rule` in the near future. The only significant change from the mechanics in `AttributeContainer` is that the `BitSet` used in the mutable case is replaced with a `byte[]` to keep field types the same as in the frozen case. Attribute-related methods in `Rule` are grouped together. PiperOrigin-RevId: 516398753 Change-Id: I0a2b479e40910ca3dced329e08a4779e35a27492
{Fast, Correct} - Choose two
Build and test software of any size, quickly and reliably.
Speed up your builds and tests: Bazel rebuilds only what is necessary. With advanced local and distributed caching, optimized dependency analysis and parallel execution, you get fast and incremental builds.
One tool, multiple languages: Build and test Java, C++, Android, iOS, Go, and a wide variety of other language platforms. Bazel runs on Windows, macOS, and Linux.
Scalable: Bazel helps you scale your organization, codebase, and continuous integration solution. It handles codebases of any size, in multiple repositories or a huge monorepo.
Extensible to your needs: Easily add support for new languages and platforms with Bazel's familiar extension language. Share and re-use language rules written by the growing Bazel community.
Follow our tutorials:
To report a security issue, please email security@bazel.build with a description of the issue, the steps you took to create the issue, affected versions, and, if known, mitigations for the issue. Our vulnerability management team will respond within 3 working days of your email. If the issue is confirmed as a vulnerability, we will open a Security Advisory. This project follows a 90 day disclosure timeline.
See CONTRIBUTING.md