Remove loop's result value(s).
#742
Closed
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.
Following up on discussion in #741, this PR proposes removing loop's exit value. If branch arities are moved to
blockandifas proposed, this change eliminates the need forloopto also have an arity immediate, which would simplify a common validation strategy.I expect this change to have little negative effect on code size or expressiveness, because
(loop x y)could usually be written as(loop x) y, and the change would also eliminate an immediate field on everyloop.