Optimizations to `aspect_hints` attribute.

This change introduces a new `required_aspect_hints_providers` parameter to the `aspect` function.

With this change (and the associated flag enabled), the `aspect_hints` attribute is evaluated differently from other attributes: A target `T` in the `aspect_hints` attribute of a target `P` is added as a dependency of `P` only if the rule class of `T` declares providers that satisfy the `required_aspect_hints_providers` of one or more aspects being applied to `P`.

The providers to be matched against an aspect's `required_aspect_hints_providers` must be declared in the rule class (via the `provides` argument of `rule()`) so that targets and aspects can be matched without actually evaluating the target. This avoids analysis time, memory usage, configuration mismatches, conformance test failures, etc. That is, it is not sufficient to just return the provider from the rule implementation function.

This behavior is enabled with the `--incompatible_require_matching_aspect_hints_providers` flag.

PiperOrigin-RevId: 947974548
Change-Id: Iba5cd12629fec0f7bb4dc346f087ea33d7568e2a
12 files changed
tree: d8acd35b6d3cd863f780d310053373d2c38addb9
  1. .bazelci/
  2. .devcontainer/
  3. .gemini/
  4. .github/
  5. docs/
  6. examples/
  7. scripts/
  8. site/
  9. src/
  10. third_party/
  11. tools/
  12. .bazelrc
  13. .bazelversion
  14. .gitattributes
  15. .gitignore
  16. AGENTS.md
  17. AUTHORS
  18. bazel_downloader.cfg
  19. BUILD
  20. CHANGELOG.md
  21. CODE_OF_CONDUCT.md
  22. CODEOWNERS
  23. combine_distfiles.py
  24. combine_distfiles_to_tar.sh
  25. compile.sh
  26. CONTRIBUTING.md
  27. CONTRIBUTORS
  28. distdir.bzl
  29. extensions.bzl
  30. LICENSE
  31. maven_install.json
  32. MODULE.bazel
  33. MODULE.bazel.lock
  34. oneversion_allowlist.csv
  35. oneversion_allowlist_for_tests.csv
  36. pyproject.toml
  37. README.md
  38. repositories.bzl
  39. requirements.txt
  40. SECURITY.md
README.md

Bazel

{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.

Getting Started

Documentation

Reporting a Vulnerability

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.

Contributing to Bazel

See CONTRIBUTING.md

Build status