Compiler: loops no longer absorb the entire continuation #1334
Conversation
This file contains hidden or 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
hhugo
changed the title
hhugo
force-pushed
the
exit-loop-early
branch
9 times, most recently
from
ac1985e to
0417d84
Compare
hhugo
force-pushed
the
exit-loop-early
branch
3 times, most recently
from
494d8d2 to
1a86c20
Compare
hhugo
force-pushed
the
exit-loop-early
branch
2 times, most recently
from
80ba4bc to
b9110d6
Compare
hhugo
force-pushed
the
exit-loop-early
branch
from
b9110d6 to
3b07e18
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
based on #1333.
The current implementation exits a loop as soon as possible. The generated code would be better if we allowed part of the continuations to remains inside the for-loop.
TODO: rebase on top of #1496