| commit | d6b9459d2c3d90fba775dbe2f3478aeeb0b2f65a | [log] [tgz] |
|---|---|---|
| author | jhorvitz <jhorvitz@google.com> | Fri Oct 15 10:24:15 2021 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Fri Oct 15 10:25:30 2021 -0700 |
| tree | 0c627fe22550c2476486905b216d03ce9fc7fbeb | |
| parent | 4442bb925b66ecb82865306976dcf32aab754dce [diff] |
In `RequiredConfigFragmentsProvider.Builder`, use a set merging strategy that promotes reuse of existing `ImmutableSet` instances, and intern the built result. This strategy virtually eliminates all memory overhead of `--include_config_fragments_provider=transitive` since there is only a small number of unique instances. It also vastly reduces the cost of building up the sets in the first place. I considered using `NestedSet`, but it would have still required some special handling because a) there are many duplicate elements at each level and b) we want to support `hashCode`/`equals` (for interning and also a trimming cache). Unlike `NestedSet`, `ImmutableSet` has a fast hash code. PiperOrigin-RevId: 403406704
{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
