Skip to content

[Constraint solver] Exit immediately from solve() if we already have … #8284

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
Mar 23, 2017
Merged

[Constraint solver] Exit immediately from solve() if we already have … #8284

merged 1 commit into from
Mar 23, 2017

Conversation

rudkx
Copy link
Contributor

@rudkx rudkx commented Mar 22, 2017

…a failed constraint.

As solveRec() already does, exit immediately if we have a failed
constraint from constraint generation. Not doing so means that we can
create a SolverScope in constraint propagation, and on destruction of
that SolverScope we clear out the failedConstraint field, obscuring the
fact that we had a failure.

…a failed constraint.

As solveRec() already does, exit immediately if we have a failed
constraint from constraint generation. Not doing so means that we can
create a SolverScope in constraint propagation, and on destruction of
that SolverScope we clear out the failedConstraint field, obscuring the
fact that we had a failure.
@rudkx
Copy link
Contributor Author

rudkx commented Mar 22, 2017

@swift-ci Please smoke test and merge

1 similar comment
@rudkx
Copy link
Contributor Author

rudkx commented Mar 23, 2017

@swift-ci Please smoke test and merge

@swift-ci swift-ci merged commit c424f51 into swiftlang:master Mar 23, 2017
@rudkx rudkx deleted the assert-on-failed-constraint branch March 23, 2017 02: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.

2 participants