tree 9c8ed42a06821454e8c31e778f87d19de6271e9e
parent e114d8a04fe07dd32fee41b3cd2e5794f10a5a9d
author Googler <noreply@google.com> 1561954244 -0700
committer Copybara-Service <copybara-worker@google.com> 1561954308 -0700

Automated rollback of commit e114d8a04fe07dd32fee41b3cd2e5794f10a5a9d.

*** Reason for rollback ***

TAP has detected 10 or more targets failed to build at https://github.com/bazelbuild/bazel/commit/e114d8a04fe07dd32fee41b3cd2e5794f10a5a9d.

TO ROLLFORWARD (without additional approval): Use[]

To see all broken targets visit []
To prevent noise from flakes, TAP double-checked the following target fails to build:
[]
but used to build fine:
[]

Questions? Comments? See the URL:[]

*** Original change description ***

bazel syntax: don't use exceptions for control flow

Previously, break, continue, and return were implemented by
throwing and catching exceptions.

Now, the Eval.exec methods return a token to indicate the
continuation: one of PASS, BREAK, CONTINUE, or RETURN.
In addition, the return value is saved in the Eval,
which is good for only one function invocation.

This is simpler (and slightly more efficient).

Also:
- FlowStatement now includes PASS too; PassStatement is gone.
- ReturnException is g...

***

PiperOrigin-RevId: 255883540