[Civl] Fixed bug in typechecking of yielding loops #877
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Each loop in a yield procedure is allowed to yield up to a yielding layer that is bounded by the disappearance layer of the enclosing yield procedure. This yielding layer N is either specified directly in an annotation on the loop header that looks like
or it is inferred.
The inference is done separately for each loop.
The bug was that the result of the inference for one loop was polluting the result for another. The problem is fixed by moving the
yieldingLayer
variable inside the iteration.