-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
[experiment] Use the new solver in coherence #110670
[experiment] Use the new solver in coherence #110670
Conversation
@bors try |
⌛ Trying commit 7739419 with merge 09171ae38e9a9e7cfe40516b634dc103a207077f... |
💔 Test failed - checks-actions |
The job Click to see the possible cause of the failure (guessed by this bot)
|
☔ The latest upstream changes (presumably #111231) made this pull request unmergeable. Please resolve the merge conflicts. |
r? @lcnr |
@@ -173,6 +173,7 @@ impl<'a, 'tcx> EvalCtxt<'a, 'tcx> { | |||
}; | |||
let (ref infcx, goal, var_values) = tcx | |||
.infer_ctxt() | |||
.with_new_solver() |
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.
would be cool to land this as yet another -Z
flag, e.g. -Ztrait-solver=next-coherence
or whatever
This is totally for funsies and not a serious attempt to migrate the compiler to use the new solver in coherence. Mostly, I'm just trying to see if we can run crater to discover any questionable behaviors with the new solver's coherence mode.
r? @ghost