-
Notifications
You must be signed in to change notification settings - Fork 10.5k
Miscellaneous solver cleanups #77178
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
Miscellaneous solver cleanups #77178
Conversation
Most constraints don't have a fix, so we can tail-allocate the fix. This saves 16 bytes per constraint, because it also eliminates some padding.
OverloadChoice is rather large, 40 bytes.
…tem::generateOverloadConstraints()
These functions are never called while undoing a change; so we want to assert if we have an active undo instead of silently not recording the change.
…containing ParameterizedProtocolType This fixes a soundness hole. We can't just match up the primary associated types of different protocols.
61a8243
to
8beaa7b
Compare
@swift-ci Please smoke test |
@swift-ci Please test source compatibility |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I feel like I reviewed most of these changes before :)
IsIsolated(false), | ||
: Kind(Kind), HasFix(false), HasRestriction(false), IsActive(false), | ||
IsDisabled(false), IsDisabledForPerformance(false), RememberChoice(false), | ||
IsFavored(false), IsIsolated(false), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I’d appreciate if we could land some of these after favoring changes since it takes time to rebase all these small changes in a proper way because favoring changes modify places in CSStep and Constraint…
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok sure
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually I checked and this PR does not cause any conflicts with solver-perf, however there is a trivial conflict currently because of this that already landed on main: e0b6a96
@swift-ci Please test Windows |
No description provided.