| commit | 794ead98f17d85ae79784c975308670eef1cc641 | [log] [tgz] |
|---|---|---|
| author | Googler <shahan@google.com> | Tue Feb 13 07:11:01 2024 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Tue Feb 13 07:12:25 2024 -0800 |
| tree | 55635d38afe5b5db8b1050386961ab6ed81b1cbb | |
| parent | be01729aa4dc86715b5a6f48127492a6029d09b5 [diff] |
Delete deserializeFully and add custom DeferredValue for DeferredObjectCodec.
* During implementation, it became clear that deserializeFully would add a lot
of avoidable complexity. Instead, the semantics are now that deserialize is
always deserializeFully except in the case of cycles, where deserialization
must be partial anyway.
* The new custom DeferredValue type instead of a Supplier achieves two things.
1. Serialization code can treat DeferredValue as a special sentinel type
that we know doesn't occur in serialized objects.
2. DeferredValue extends Callable, so it can be directly added to Futures
callbacks, saving extra allocations.
PiperOrigin-RevId: 606611049
Change-Id: I0c91630b27528caad8e5ccfaba31f2399310d4eb
{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
