| commit | 8002df18400f77554fe7ea9628eb2db74468b1d4 | [log] [tgz] |
|---|---|---|
| author | wyv <wyv@google.com> | Mon May 09 05:39:03 2022 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Mon May 09 05:40:48 2022 -0700 |
| tree | a7d5ab7e3aac002c117c606e15da9dcd7584cec6 | |
| parent | 5a7f86c8036ba0c69f0a18be0a02051ccf3bbc7d [diff] |
Cleanup in StarlarkRuleClassFunctions - Removed the TODO about labelCache being copied from ConfiguredRuleClassProvider. The latter no longer has such a cache, so the TODO is outdated anyways. Replaced with a more descriptive comment. - labelCache now uses the new Label#parseCanonical method. - Removed an unused constructor. - The `label` function now uses the new Label#parseWithRepoContext method and is no longer "surprisingly complex". Note that we don't actually need to cache these labels since calls to `Label(...)` are fairly rare. PiperOrigin-RevId: 447445194
{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
