| commit | d51a88fdc43636e995bb3e34fd2881c5010b9920 | [log] [tgz] |
|---|---|---|
| author | mgeisler <mgeisler@google.com> | Fri Apr 09 06:17:17 2021 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Fri Apr 09 06:18:51 2021 -0700 |
| tree | e9c87863d08752aef997fe2f557dd2581ba77b6d | |
| parent | cf9f89cf1f818e468da7e2293055ba2b92e45e2f [diff] |
Simplify build failure output by always using `NNN arguments` (plural) When Blaze reports a compilation error, it shows the first bit of the command line used to invoke the compiler. When more than 200 characters have been shown (`APPROXIMATE_MAXIMUM_MESSAGE_LENGTH`), the rest of the command line is shown as: ``` (remaining NNN argument(s) skipped) ``` When I see the message in my console, it's normally because 100+ arguments are being skipped. So the correct form is then: ``` (remaining NNN arguments skipped) ``` I find this more readable since it avoids a nested parenthesis and it uses the correct plural form. Put differently, the `argument(s)` form is asking the reader to do the mental work of selecting between `argument` and `arguments` — which is unnecessary in the vast majority of cases. RELNOTES: Simplify build failure output by always using `NNN arguments`. PiperOrigin-RevId: 367620498
{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
