-
Notifications
You must be signed in to change notification settings - Fork 13.3k
detect additional uses of opaques after writeback #140641
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
base: master
Are you sure you want to change the base?
Conversation
Some changes occurred to the core trait solver cc @rust-lang/initiative-trait-system-refactor |
f270507
to
8fe59d0
Compare
This comment has been minimized.
This comment has been minimized.
8fe59d0
to
4b89483
Compare
☔ The latest upstream changes (presumably #140682) made this pull request unmergeable. Please resolve the merge conflicts. |
4b89483
to
99cf4e8
Compare
These commits modify the If this was unintentional then you should revert the changes before this PR is merged. |
r=me after base pr lands |
@rustbot blocked |
Based on #140607. It's a lot harder to encounter in practice than I though 😅 😁 I've still added it with the expectation that somebody will encounter it at some point.
Also modifies the
EvalCtxt
to use the same impl to detect newly added opaque types.r? @compiler-errors