Deduplicate MergedConfiguredTarget instances across dependency edges. `AbstractConfiguredTarget` overrides `hashCode()` based on target label and configuration key so that `ConfiguredTarget` instances placed in Starlark dicts have deterministic hash codes, while leaving `equals()` as reference equality (`Object.equals`). Because `MergedConfiguredTarget` is created freshly for every incoming dependency edge during aspect propagation, placing aspect-decorated dependencies into a Starlark `depset` or `dict` fails to deduplicate across edges and causes all incoming edges for the same target to collide in the same hash bucket during `depset.to_list()`. Overriding `equals()` on `MergedConfiguredTarget` to compare the underlying base target and attached aspects (while retaining `AbstractConfiguredTarget`'s deterministic `hashCode()`) allows Starlark `depset`s and `dict`s to deduplicate aspect-decorated targets across edges in O(1) time without regressing hash determinism. RELNOTES: None. PiperOrigin-RevId: 1009072109 Change-Id: Ied88e64c4a508fe1b53cff851acec4c6280d3019
{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.
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
