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.
Now that we've restricted
Ref
s to parameters and local variables as of #64, there's no real reason for instructions introducingRef
scopes to require their own blocks; we can just introduce the scope in an instruction and then resolve it in another instruction later in the same block. I think I had also previously thought that this would make validation harder in #53, but now I no longer think that's the case; all you need to do is mark reference variables using the same scope as expired once you reach the "resolve" instruction. Anyway, this will make #86 easier because it means that a function's level of nesting can no longer drastically increase during transposition.