-
Notifications
You must be signed in to change notification settings - Fork 13.4k
Don't require rigid alias's trait to hold #139828
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
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,41 @@ | ||
//@ edition: 2024 | ||
//@ revisions: current next | ||
//@ ignore-compare-mode-next-solver (explicit revisions) | ||
//@[next] compile-flags: -Znext-solver | ||
//@ check-pass | ||
|
||
// Regression test for <https://github.com/rust-lang/trait-system-refactor-initiative/issues/177>. | ||
// Coroutines erase all free lifetimes from their interior types, replacing them with higher- | ||
// ranked regions which act as universals, to properly represent the fact that we don't know what | ||
// the value of the region is within the coroutine. | ||
// | ||
// In the future in `from_request`, that means that the `'r` lifetime is being replaced in | ||
// `<T as FromRequest<'r>>::Assoc`, which is in present in the existential bounds of the | ||
// `dyn Future` that it's awaiting. Normalizing this associated type, with its free lifetimes | ||
// replaced, means proving `T: FromRequest<'!0>`, which doesn't hold without constraining the | ||
// `'!0` lifetime, which we don't do today. | ||
|
||
// Proving `T: Trait` holds when `<T as Trait>::Assoc` is rigid is not necessary for soundness, | ||
// at least not *yet*, and it's not even necessary for diagnostics since we have other special | ||
// casing for, e.g., AliasRelate goals failing in the BestObligation folder. | ||
|
||
// The old solver unintentioanlly avoids this by never checking that `T: Trait` holds when | ||
// `<T as Trait>::Assoc` is rigid. Introducing this additional requirement when projecting rigidly | ||
// in the old solver causes this (and tons of production crates) to fail. See the fallout from the | ||
// crater run at <https://github.com/rust-lang/rust/pull/139763>. | ||
|
||
use std::future::Future; | ||
use std::pin::Pin; | ||
|
||
pub trait FromRequest<'r> { | ||
type Assoc; | ||
fn from_request() -> Pin<Box<dyn Future<Output = Self::Assoc> + Send>>; | ||
} | ||
|
||
fn test<'r, T: FromRequest<'r>>() -> Pin<Box<dyn Future<Output = ()> + Send>> { | ||
Box::pin(async move { | ||
T::from_request().await; | ||
}) | ||
} | ||
|
||
fn main() {} |
Oops, something went wrong.
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.
Uh oh!
There was an error while loading. Please reload this page.