Allow //visibility:public and //visibility:private in non-singleton visibility declarations ... but simplify the resulting visibility appropriately when saving the visibility attribute: $foo plus public is public; $foo plus private is $foo; and an empty visibility list is canonicalized to ["//visibility:private"]. This makes it easier for symbolic macros to grant visibilities on targets that they declare. Work toward https://github.com/bazelbuild/bazel/issues/19922. The canonicalization of an empty visibility list to ["//visibility:private"] is technically an incompatible change affecting query output, but is very unlikely to break anything in practice. RELNOTES: Non-singleton target visibility lists can now contain "//visibility:public" and "//visibility:private" elements; the result is appropriately simplified when assigned to an attribute: ["//foo:__subpackages__", "//visibility:public"] is saved as ["//visibility:public"], ["//foo:__subpackages__", "//visibility:private"] is saved as ["//foo:__subpackages__"], and for consistency's sake, an empty target visibility list [] is saved as ["//visibility:private"]. PiperOrigin-RevId: 680761159 Change-Id: Ic2edaf13dfe48b0f0014d404ced34aa7632d33c7
{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