Emit function param's role in starlark_doc_extract proto output ... and clarify the order of parameters in the list. Note that we have two reasonable possibilities: * declaration order, e.g. foo(pos, *args, kwonly, **kwargs) * calling convention order, e.g. foo(pos, kwonly, *args, **kwargs) For backwards compatibility, and to avoid confusion since we do not emit the `*` marker between positional and keyword-only params, it makes more sense to use the latter. Users such as the Stardoc markdown renderer can easily transform it into declaration order if desired. Working towards https://github.com/bazelbuild/stardoc/issues/225 PiperOrigin-RevId: 638390032 Change-Id: I201d89bc3451a98a02905722800c78cd3d09e5b7
{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:
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
