Skip to content

DestroyHoisting: handle infinite loops correctly #28381

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Nov 20, 2019

Conversation

eeckstein
Copy link
Contributor

Ignore blocks in infinite loops and don't insert destroys where they don't belong.

Fixes an ownership verifier crash.

Ignore blocks in infinite loops and don't insert destroys where they don't belong.

Fixes an ownership verifier crash.
@eeckstein
Copy link
Contributor Author

@swift-ci smoke test and merge

return exitReachability == ExitReachability::ReachesExit;
}

bool isInInfiniteLoop() const {

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just for cosmetically, as for the function names, maybe reachesExit() and reachesInfinityLoop() are better

@swift-ci swift-ci merged commit 747f3ff into swiftlang:master Nov 20, 2019
@eeckstein eeckstein deleted the fix-destoy-hoisting branch November 20, 2019 12:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants