| commit | b08585cea8e6451d16d584ace1bafee882d88378 | [log] [tgz] |
|---|---|---|
| author | brandjon <brandjon@google.com> | Fri Feb 06 12:36:18 2026 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Fri Feb 06 12:37:40 2026 -0800 |
| tree | 67ca4f0b8494bbae4dcdfa0c10a8dca68fe8b53e | |
| parent | eb234b1d9ccd250df8837c8ec225db944ce661c7 [diff] |
Eliminate all hardcoded usage of the type universe in `Module` This follows up on unknown commit to obtain the remaining type constructors from their runtime symbols, rather than from the map in `Types.java`. For most of the types, this is just a matter of adding `isTypeConstructor = true` and a corresponding static `getBaseTypeConstructor()`. Special handling is needed in `CallUtils` for boolean since it's a builtin Java type, similar to the special casing for `String` -> `StringModule`. The abstract types `Collection`, `Sequence`, and `Mapping` are not currently defined as actual symbols in the universe, so their usage in `DynamicTypeCheckTest` requires that they be added to the mock environment (`None` no longer suffices as a mock value). Work toward #28325. PiperOrigin-RevId: 866570905 Change-Id: I4544a82ef014922bfc3809b9885097885fd1e31d
{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
