-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
fix NLL ICEs #53580
fix NLL ICEs #53580
Conversation
r? @cramertj (rust_highfive has picked a reviewer for you, use r? to override) |
r? @pnkfelix |
The job Click to expand the log.
I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
dfd180a
to
6b87695
Compare
I marked this as WIP because:
|
The job Click to expand the log.
I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
@TimNN jfyi, the output extracted was less than helpful :)
No clue why... |
the problem turned out to be that this was a case of UI tests that were supposed to fail...not failing. (Because I was missing a |
51fa9e1
to
a59584a
Compare
OK, I've changed my mind. I think this PR is ready to land. I would still like to do some refactoring -- in particular, I am not happy with the way that the trait queries + type-op setup is so distinct, but I think that is best left to a separate PR. |
I was about to file a dupe of #53680 and have verified that this PR fixes my ICE - thanks for putting it together! |
@bors r+ |
📌 Commit a59584a has been approved by |
fix NLL ICEs Custom type-ops reuse some of the query machinery -- but while query results are canonicalized after they are constructed, custom type ops are not, and hence we have to resolve the type variables to avoid an ICE here. Also, use the type-op machinery for implied outlives bounds. Fixes #53568 Fixes #52992 Fixes #53680
☀️ Test successful - status-appveyor, status-travis |
Custom type-ops reuse some of the query machinery -- but while query results are canonicalized after they are constructed, custom type ops are not, and hence we have to resolve the type variables to avoid an ICE here.
Also, use the type-op machinery for implied outlives bounds.
Fixes #53568
Fixes #52992
Fixes #53680