| commit | d5a1bc4524830da6c20f771a80694a8995711377 | [log] [tgz] |
|---|---|---|
| author | brandjon <brandjon@google.com> | Wed Jan 14 12:21:58 2026 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed Jan 14 12:23:04 2026 -0800 |
| tree | 5db19ad412d919e81d25436f9b689743af295aa5 | |
| parent | d34d6389adb8848e55626b4b45667c3278772c51 [diff] |
Rename TypeResolver and related concepts for clarity Calling it "TypeResolver" has always been dubious because it requires you to disambiguate between "resolving" an AST and "type-resolving" it in comments. This CL renames it to "TypeTagger" (verb form "type-tagging an AST"). This CL also renames the `evalType` method to `extractType` to make it clearer that this is a static operation (and not particularly complicated or intensive), and makes the static entry point to that method an overload with identical name. Work toward #27728. PiperOrigin-RevId: 856317088 Change-Id: Ib3ed9e251f8c5f4be02faecb3f25fbf7ddfb21e1
{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
