| commit | 380d35e4e4d937151380cc0e4de895d461ffac38 | [log] [tgz] |
|---|---|---|
| author | Googler <jingwen@google.com> | Thu Jun 06 22:06:11 2024 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu Jun 06 22:07:49 2024 -0700 |
| tree | 92db228b08273050abec91c82cf5931ce1b6727e | |
| parent | 08ef9b200d1b62ed66e10d89d32c709b70e7adbd [diff] |
Refactor `FlagSetFunction` to depend on a `ProjectValue` directly, instead of depending on its own `BzlLoadValue`. The dependency chain is now `FlagSetFunction` -> `ProjectFunction` -> `BzlLoadFunction`. `FlagSetFunction` is kept distinct from `ProjectFunction` so as to not burden other reverse dependencies of `ProjectFunction` from the extra Skyframe lookup costs from `FlagSetFunction` (i.e. `ParsedFlagsFunction`). `ProjectFunction` is implemented as an indirection to `BzlLoadValue`, so there's a place for PROJECT.scl specific validations and getters in the future. PiperOrigin-RevId: 641126914 Change-Id: I4e799395817c8d0f96a0af3e6c6520b29fafdf08
{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
