Migrate ImmutableListCodec off of Unsafe. ImmutableListCodec still registers the list before deserializing its elements, to support cycles, but no longer uses Unsafe.allocateInstance or Unsafe.putObject. * Lists with two or more elements are created by calling the package-private RegularImmutableList constructor through a MethodHandle obtained with MethodHandles.privateLookupIn. The constructor wraps the given array without copying, so elements are deserialized directly into it. This is possible because Guava is in an unnamed module. * Lists with a single element are created with ImmutableList.of(placeholder), and the final SingletonImmutableList.element field is overwritten once the actual element is available, through a MethodHandle from Lookup.unreflectSetter. This is subject to JEP 500 restrictions on final field mutation. This also removes one of the remaining callers of the offset-based AsyncDeserializationContext.deserialize overload. PiperOrigin-RevId: 1008904532 Change-Id: Idfcb147c3889e5df288907b436a372aaa81d7cf9
{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
