Intern unresolved symlink targets (#31122) `UnresolvedSymlinkAction` interns its destination string in the constructor. Actions with the same destination share string storage without changing the raw target value, action key, or deferred `PathFragment` conversion. One matched pair of partial monorepo analyses retained 3.27 million fewer strings and backing arrays, accounting for about 664 MB in the class histogram. Reported after-GC heap was 676 MB lower; analysis time and peak RSS were essentially unchanged. This is a single comparison, not a repeatability claim. Validation on upstream master: all six `UnresolvedSymlinkActionTest` cases pass, covering action keys, symlink creation, and serialization. RELNOTES: None -zbarskybot Closes #31122 COPYBARA_INTEGRATE_REVIEW=https://github.com/bazelbuild/bazel/pull/31122 from dzbarsky:codex/symlink-targets-upstream 9f444949636d5a953d7ad10c3bc8f978f79988ce PiperOrigin-RevId: 981263379 Change-Id: I0e825a11a001568b5c19e83b81c8e70959bdc905
{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
