Skip to content

[Constraint solver] Move all partitioning into partitionDisjunction #23114

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

Conversation

DougGregor
Copy link
Member

Centralize the various attempts to partition an overload set into ConstraintSystem::partitionDisjunction(), so we have a single place where this logic can be reasoned about and updated.

…oning

This narrow favoring rule makes more sense as part of disjunction
partitioning, because it is not dependent on the use site at all and
should only kick in when other options fail.
…partitioning

Continuing along my path to move application-independent partitioning
rules into the common disjunction partitioning code.
@DougGregor
Copy link
Member Author

@swift-ci please smoke test and merge

Copy link
Contributor

@xedin xedin left a comment

Choose a reason for hiding this comment

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

Nice!

@DougGregor
Copy link
Member Author

@swift-ci please smoke test macOS

1 similar comment
@DougGregor
Copy link
Member Author

@swift-ci please smoke test macOS

@DougGregor DougGregor force-pushed the constraint-solver-partition-cleanup branch from 6e1f3ab to fd50d94 Compare March 6, 2019 05:44
@DougGregor
Copy link
Member Author

@swift-ci please smoke test and merge

1 similar comment
@DougGregor
Copy link
Member Author

@swift-ci please smoke test and merge

@swift-ci swift-ci merged commit 0e1c761 into swiftlang:master Mar 6, 2019
@DougGregor DougGregor deleted the constraint-solver-partition-cleanup branch March 6, 2019 07:00
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