The great Skylark -> Starlark class migration: SkylarkLateBoundDefault SkylarkInterfaceUtils SkylarkModule -> StarlarkBuiltin SkylarkModuleCategory -> StarlarkDocumentationCategory SkylarkInterfaceUtilsTest This change is unusually large - apologies. 111 files in the copybara project reference SkylarkModule and SkylarkModuleCategory. These also constitute the vast majority of changes in the Bazel project. I could alternatively reduce this change just to those symbols, due to the size and cross-project impact. But the other symbols really don't make much of a difference. I could also *add* to this change by also replacing SkylarkCallable, which is also in most of these files. But I don't know how much larger that will make the change and I fear it's already hitting its reasonable limits. PiperOrigin-RevId: 309428973
{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
