Fix memory regression in RuleVisibility Benchmarks show that https://github.com/bazelbuild/bazel/commit/cd82f68cfdf44aabaea1931ea9ff870ec7bb4af1 introduced a memory regression. Fix it by: * memoizing the very frequently used ["//visibility:public"] and ["//visibility:private"] declared labels lists * for filtering out private labels, using a list builder with a known expected size instead of relying on the streams api I also experimented with feeding the simplified visibility label lists back into the package builder's list interner - but decided against it because benchmarks show it results in a slightly higher memory usage. PiperOrigin-RevId: 681511741 Change-Id: I498e4adca976834d6b137b106f9d202c793bb54d
{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
