Issue 52057 — inference variable#52731
Conversation
|
A note on naming: I want to rename I wound up not doing the rename in this PR though because it would conflict so badly with #52488 |
|
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 |
|
@bors p=1 -- this is a major blocker for NLL + EP2 in terms of causing ICEs and errors |
5dbcb11 to
03ea954
Compare
|
Ping from triage @pnkfelix! This PR needs your review. |
There was a problem hiding this comment.
I'll not block review on this, but I'm sort of surprised you went with a Vec<Ty> with special case info about the last element rather than a (Vec<Ty>, Ty) ...
|
r=me since there are conflicts and niko is on PTO, I might take a shot at resolving the conflicts myself |
|
conflicts! That's what you get for trying to opt into new features! |
This duplicates, effectively, existing code in the universal regions computation.
Normalization results are memoized, so this may not be worth it, but it seems easy enough to do.
03ea954 to
b9652ae
Compare
|
@bors r+ |
|
📌 Commit b9652ae has been approved by |
…=pnkfelix Issue 52057 — inference variable Break out the computation of universal region relations and do it during the typeck, where we can handle the resulting constraints that arise. r? @pnkfelix
|
☀️ Test successful - status-appveyor, status-travis |
Break out the computation of universal region relations and do it during the typeck, where we can handle the resulting constraints that arise.
r? @pnkfelix