When a fetch for an Object[] returns, cache the unwrapped contents. By keeping the cached value as the wrapping ListenableFuture<Object[]>, we have the potential of making multiple fetches for the same fingerprint. This is illustrated by the test case - a fetch for a transitive member will only retain the ListenableFuture until it is resolved, then the cache entry becomes eligible for GC even though the underlying Object[] is still in memory. I don't know how often this happens, but the change seems harmless and we can use the number of NestedSet reads to see if it makes any difference. RELNOTES: None. PiperOrigin-RevId: 298361983
{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:
See CONTRIBUTING.md
