-
Notifications
You must be signed in to change notification settings - Fork 13.4k
Hack: Ignore inference variables in certain queries #86866
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
Show all changes
10 commits
Select commit
Hold shift + click to select a range
1297cb7
add test case
nikomatsakis 6f4b539
introduce helper function
nikomatsakis 26f7030
remove unused Option
nikomatsakis 40ee019
allow inference vars in type_implements_trait
nikomatsakis 75c1722
be conservative in has_significant_drop
nikomatsakis 9bdfde0
remove some ad-hoc has_infer_types checks that aren't needed anymore
nikomatsakis 86a5a65
Update compiler/rustc_middle/src/ty/normalize_erasing_regions.rs
nikomatsakis 63fbefd
tag issues with FIXME
nikomatsakis 1c1573d
remove outdated comment
nikomatsakis 492ba34
revert broken formatting
nikomatsakis 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
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,16 @@ | ||
// edition:2018 | ||
|
||
fn main() { | ||
|
||
} | ||
|
||
async fn foo() { | ||
// Adding an .await here avoids the ICE | ||
test()?; | ||
//~^ ERROR the `?` operator can only be applied to values that implement `Try` | ||
//~| ERROR the `?` operator can only be used in an async function that returns | ||
} | ||
|
||
// Removing the const generic parameter here avoids the ICE | ||
async fn test<const N: usize>() { | ||
} |
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,28 @@ | ||
error[E0277]: the `?` operator can only be applied to values that implement `Try` | ||
--> $DIR/issue-84841.rs:9:5 | ||
| | ||
LL | test()?; | ||
| ^^^^^^^ the `?` operator cannot be applied to type `impl Future` | ||
| | ||
= help: the trait `Try` is not implemented for `impl Future` | ||
= note: required by `branch` | ||
|
||
error[E0277]: the `?` operator can only be used in an async function that returns `Result` or `Option` (or another type that implements `FromResidual`) | ||
--> $DIR/issue-84841.rs:9:11 | ||
| | ||
LL | async fn foo() { | ||
| ________________- | ||
LL | | // Adding an .await here avoids the ICE | ||
LL | | test()?; | ||
| | ^ cannot use the `?` operator in an async function that returns `()` | ||
LL | | | ||
LL | | | ||
LL | | } | ||
| |_- this function should return `Result` or `Option` to accept `?` | ||
| | ||
= help: the trait `FromResidual<_>` is not implemented for `()` | ||
= note: required by `from_residual` | ||
|
||
error: aborting due to 2 previous errors | ||
|
||
For more information about this error, try `rustc --explain E0277`. |
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.
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.
We use this also in the trait migration part of the code, I think we should do must_apply_modulo_regions there as well
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.
cc @roxelo
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.
Ignore this, the other method is
ty_implements_trait
which uses a different query.