commit | a1f90ce376a82a862ffb7180e39f8f13e64488f6 | [log] [tgz] |
---|---|---|
author | shreyax <shreyax@google.com> | Thu Feb 15 12:05:13 2018 -0800 |
committer | Copybara-Service <copybara-piper@google.com> | Thu Feb 15 12:07:08 2018 -0800 |
tree | ca325b7e8c1ec972a4c8bb2903cc51e61e8fad46 | |
parent | f70aff52a529b3f3b71e8179e52fc2b06835275c [diff] |
Don't intern PathFragments when we create PackageIdentifiers. This should be a strict win: There are only two places Canonicalizer did PathFragment interning: PackageIdentifier creation and Package creation. PackageIdentifiers are always interned by a separate interner, and so the underlying PathFragment will be in 1-1 correspondence with PackageIdentifiers (per repo). Moreover, Packages are created with a PackageIdentifier already existing, so it will use the same PathFragment of the unique PackageIdentifier. PiperOrigin-RevId: 185877942
{Fast, Correct} - Choose two
Build and test software of any size, quickly and reliably.
Speed up your builds and tests: Bazel only rebuilds 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
Bazel is released in ‘Beta’. See the product roadmap to learn about the path toward a stable 1.0 release.