[rolling] Automated rollback of commit c55094c964c696289814e1f2503534a8f8e6a3eb. (#30477) Cherry-pick of e3df6b31d80c14af563b887bf3d206e871fd836e; test failures on rolling branch: https://buildkite.com/bazel/bazel-bazel/builds/36293/canvas?jid=019fa3bd-dcfd-4e4a-8cf8-d19f88840c9d&tab=output --- *** Reason for rollback *** This change is breaking our postsubmit: https://buildkite.com/bazel/bazel-bazel/builds/36178#_ both: bazel_bootstrap_distfile_test and bazel_bootstrap_distfile_tar_test are failing on many platforms *** Original change description *** Support type aliases This requires introducing open-term type arguments (this means type variables and type applications / unions using type variables, plus allowing dict type arguments to have open terms as their values) which are evaluated by a special composite type constructor. The type constructors defined by an alias get stored in the type table in the same way as load()-ed type constructors; and at eval time, are wrapped in a TypeConstructorValue for exporting to other modules. Working... *** PiperOrigin-RevId: 950849625 Change-Id: Ib259e32539ec82c8ad03d9ef1756ded248b17137 <!-- Thank you for contributing to Bazel! Please read the contribution guidelines: https://bazel.build/contribute.html --> ### Description <!-- Please provide a brief summary of the changes in this PR. --> ### Motivation <!-- Why is this change important? Does it fix a specific bug or add a new feature? If this PR fixes an existing issue, please link it here (e.g. "Fixes #1234"). --> ### Build API Changes <!-- Does this PR affect the Build API? (e.g. Starlark API, providers, command-line flags, native rules) If yes, please answer the following: 1. Has this been discussed in a design doc or issue? (Please link it) 2. Is the change backward compatible? 3. If it's a breaking change, what is the migration plan? --> No ### Checklist - [ ] I have added tests for the new use cases (if any). - [ ] I have updated the documentation (if applicable). ### Release Notes <!-- If this is a new feature, please add 'RELNOTES[NEW]: <description>' here. If this is a breaking change, please add 'RELNOTES[INC]: <reason>' here. If this change should be mentioned in release notes, please add 'RELNOTES: <reason>' here. --> RELNOTES: None Co-authored-by: salmasamy <salmasamy@google.com>
{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.
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
