-
Notifications
You must be signed in to change notification settings - Fork 13.4k
make evaluation track whether outlives relationships mattered #54401
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
Closed
Closed
Changes from 1 commit
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
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
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
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,24 @@ | ||
// Regression test for #54302. | ||
// | ||
// We were incorrectly using the "evaluation cache" (which ignored | ||
// region results) to conclude that `&'static str: Deserialize`, even | ||
// though it would require that `for<'de> 'de: 'static`, which is | ||
// clearly false. | ||
|
||
trait Deserialize<'de> {} | ||
|
||
trait DeserializeOwned: for<'de> Deserialize<'de> {} | ||
impl<T> DeserializeOwned for T where T: for<'de> Deserialize<'de> {} | ||
|
||
// Based on this impl, `&'static str` only implements Deserialize<'static>. | ||
// It does not implement for<'de> Deserialize<'de>. | ||
impl<'de: 'a, 'a> Deserialize<'de> for &'a str {} | ||
|
||
fn main() { | ||
fn assert_deserialize_owned<T: DeserializeOwned>() {} | ||
assert_deserialize_owned::<&'static str>(); //~ ERROR | ||
|
||
// It correctly does not implement for<'de> Deserialize<'de>. | ||
// fn assert_hrtb<T: for<'de> Deserialize<'de>>() {} | ||
// assert_hrtb::<&'static str>(); | ||
} |
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,17 @@ | ||
error[E0279]: the requirement `for<'de> 'de : ` is not satisfied (`expected bound lifetime parameter 'de, found concrete lifetime`) | ||
--> $DIR/hrtb-cache-issue-54302.rs:19:5 | ||
| | ||
LL | assert_deserialize_owned::<&'static str>(); //~ ERROR | ||
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | ||
| | ||
= note: required because of the requirements on the impl of `for<'de> Deserialize<'de>` for `&'static str` | ||
= note: required because of the requirements on the impl of `DeserializeOwned` for `&'static str` | ||
note: required by `main::assert_deserialize_owned` | ||
--> $DIR/hrtb-cache-issue-54302.rs:18:5 | ||
| | ||
LL | fn assert_deserialize_owned<T: DeserializeOwned>() {} | ||
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | ||
|
||
error: aborting due to previous error | ||
|
||
For more information about this error, try `rustc --explain E0279`. |
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you give an example where this subtle thing is true? It certainly seems like we are comparing freshened regions, and that should be OK: freshening does not touch LBRs (even escaping LBRs), and trait evaluation pretty much works with the staticized version of a type, ignoring non-late-bound regions.