| commit | ee3fa9dfd0aaf26a226eb6af7dceb0f55649f54a | [log] [tgz] |
|---|---|---|
| author | Googler <brandjon@google.com> | Wed Sep 25 11:42:05 2024 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed Sep 25 11:43:53 2024 -0700 |
| tree | 74e8757e716cf4bf24cb49ad8d6a2634d49fe168 | |
| parent | 62dc3b5b3b31fe53e25d253f501eeed21ab4ae48 [diff] |
Move macro visibility appending out of Package.Builder `Package.Builder` has a utility method `copyAppendingCurrentMacroLocation`, that doesn't really need to be there. Ahead of further refactoring of this class, I figured I'd spin off this method. (The purpose of the method is to determine the munged visibility values for targets declared within symbolic macros.) The method is re-expressed as two helpers in `RuleVisibility` and one in `MacroInstance`, each of which does a narrower task more suited for its new home. Made the convenience method `Builder#currentMacro` public, since it's much terser than `getCurrentMacroFrame().macroInstance`. Added a drive-by TODO in `StarlarkNativeModule`. Work toward #19922. PiperOrigin-RevId: 678786589 Change-Id: I5cc190bd6ef908a3e67094eacd13e9c91ef43d7c
{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
