Yeet propagate_ambiguity - #162935
Open
adwinwhite wants to merge 4 commits into
Open
Yeet propagate_ambiguity#162935adwinwhite wants to merge 4 commits into
propagate_ambiguity#162935adwinwhite wants to merge 4 commits into
Conversation
Collaborator
|
|
This comment has been minimized.
This comment has been minimized.
adwinwhite
force-pushed
the
abby-ambig
branch
from
September 18, 2026 06:19
cf82761 to
f5bfcf0
Compare
adwinwhite
marked this pull request as ready for review
September 18, 2026 06:48
This comment has been minimized.
This comment has been minimized.
adwinwhite
force-pushed
the
abby-ambig
branch
from
September 18, 2026 09:06
f5bfcf0 to
94e5351
Compare
BoxyUwU
reviewed
Sep 23, 2026
|
|
||
| let constraint = ((smallest_universe + 1)..=largest_universe) | ||
| .map(|u| UniverseIndex::from_usize(u)) | ||
| if !self |
Member
There was a problem hiding this comment.
Can you add a comment explaining why we use ambiguity here
Member
|
@rustbot author |
Collaborator
|
Reminder, once the PR becomes ready for a review, use |
Contributor
|
☔ The latest upstream changes (presumably #163227) made this pull request unmergeable. Please resolve the merge conflicts by rebasing. |
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes rust-lang/project-assumptions-on-binders#29
When assumptions computation fails, we want to force the goal response to be ambiguous since we can't evaluate placeholder constraints.
We used to do this via
LeafRegionConstraint::Ambiguityand propagates it everywhere.This PR simplifies that by tracking whether we should force ambiguity in a more direct way. We just check whether we have computed assumptions for relevant universes.
This also clarifies the meaning of
LeafRegionConstraint::Ambiguitywhich only represents true ambiguity (forever ambiguity no matter inference progress).This doesn't solve the problem that we're being conservative about forcing ambiguity. Maybe we can have
falses in some universes even if other universes don't have assumptions. We can be smart about this in the future.Unsure part: we can also have ambiguity from non-lifetime placeholder. Unsure what to do with that. Still trying to understand it.
r? @BoxyUwU