Builtin class and method descriptors store their `BuiltinManager` This will be used to map Java types onto `StarlarkType`s in an extensible way, rather than the current hardcoded visitation in `eval/TypeChecker#fromJava`. The manager added to `ClassDescriptor` is unused as of this CL. The manager added to `MethodDescriptor` is used to replace the `StarlarkSemantics` in `BuiltinFunction`. This change affects serialization because the `BuiltinManager` is now reachable from `BuiltinFunction` via `MethodDescriptor`. `BuiltinFunction` is only serialized when Starlark symbols are serialized, which to my knowledge only currently happens in tests. To fix the tests and help prevent this from being a blocker to further Starlark serialization, I added a `BuiltinModuleCodec` that deserializes by just looking up the `StarlarkSemantics` from skyframe. This does regrettably require making various bits of `CallUtils` public instead of package-private. Work toward #28325. PiperOrigin-RevId: 882765789 Change-Id: I6f94a6250b3dc53d3b1c2ecc2181f9b1c17daa4a
{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.
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
