commit | 77153524fb2e02b9862604f507970e18f87d1d29 | [log] [tgz] |
---|---|---|
author | lberki <lberki@google.com> | Thu Mar 19 01:16:28 2020 -0700 |
committer | Copybara-Service <copybara-worker@google.com> | Thu Mar 19 01:17:30 2020 -0700 |
tree | 83bb96bf9af5f34e5189734fc0f427d1eedde35b | |
parent | c4502cffe36b250ed965a917eff9900332f110a4 [diff] |
Merge ByteBufferFragment and ByteFragmentAtOffset and call it FileFragment. It seemed odd that the object that contains the start and end of a fragment is inside the object that contains the ByteBuffer. It's more logical the other way round, but after going this far, I realized that it's a bit nicer to not have two objects at all. RELNOTES: None. PiperOrigin-RevId: 301761088
{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