forked from bazelbuild/bazel
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
bazel analysis: don't use EvalException for non-Starlark errors
StarlarkDefinedConfigTransition.evaluate and FunctionTransitionUtils.applyAndValidate now report errors through the event handler, instead of throwing EvalException. They use the new ValidationException class for internal plumbing of non-Starlark errors. This is another step towards eliminating the EvalException(Location) constructor. Also: - inline SDCT.evalFunction - tweak error messages PiperOrigin-RevId: 350775434
- Loading branch information
1 parent
323cbc7
commit d07bf13
Showing
6 changed files
with
126 additions
and
94 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.