Save memory by not storing the parent-relative path in `TreeFileArtifact`. `TreeFileArtifact` already stores its full exec path (as all artifacts do) and its parent. The parent-relative path is not often needed and can be computed on demand. It would save even more memory to store the parent-relative path instead of the full exec path and compute the full exec path on-demand, However, the `Artifact` class hierarchy requires the full exec path to be stored in a field, and `getExecPath` is expected to be fast. To offset some garbage, `SpawnInputExpander` is modified to use the full exec path if possible instead of concatenating the parent and parent-relative path. PiperOrigin-RevId: 881414453 Change-Id: I31d571967749febe33a4dcc1da8d0577c256389f
{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
