-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
Add test for rust-lang#114912 #116256
Merged
Merged
Add test for rust-lang#114912 #116256
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
10 changes: 10 additions & 0 deletions
10
tests/ui/async-await/debug-ice-attempted-to-add-with-overflow.rs
This file contains 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,10 @@ | ||
// check-fail | ||
// edition:2021 | ||
|
||
// test for issue-114912 - debug ice: attempted to add with overflow | ||
|
||
async fn main() { | ||
//~^ ERROR `main` function is not allowed to be `async` | ||
[0usize; 0xffff_ffff_ffff_ffff].await; | ||
//~^ ERROR `[usize; usize::MAX]` is not a future | ||
} |
23 changes: 23 additions & 0 deletions
23
tests/ui/async-await/debug-ice-attempted-to-add-with-overflow.stderr
This file contains 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,23 @@ | ||
error[E0277]: `[usize; usize::MAX]` is not a future | ||
--> $DIR/debug-ice-attempted-to-add-with-overflow.rs:8:37 | ||
| | ||
LL | [0usize; 0xffff_ffff_ffff_ffff].await; | ||
| -^^^^^ | ||
| || | ||
| |`[usize; usize::MAX]` is not a future | ||
| help: remove the `.await` | ||
| | ||
= help: the trait `Future` is not implemented for `[usize; usize::MAX]` | ||
= note: [usize; usize::MAX] must be a future or must implement `IntoFuture` to be awaited | ||
= note: required for `[usize; usize::MAX]` to implement `IntoFuture` | ||
|
||
error[E0752]: `main` function is not allowed to be `async` | ||
--> $DIR/debug-ice-attempted-to-add-with-overflow.rs:6:1 | ||
| | ||
LL | async fn main() { | ||
| ^^^^^^^^^^^^^^^ `main` function is not allowed to be `async` | ||
|
||
error: aborting due to 2 previous errors | ||
|
||
Some errors have detailed explanations: E0277, E0752. | ||
For more information about an 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 do not support async main so we can remote it? of there is any reason that I am missing to add it?
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.
I was just following the issue, which I presume wanted to be tested for with the async/await if not the await itself would have to removed too.
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.
Ah I see, ok it is fine for me.
another way to write the same thing is
In this way, you have no longer the problem of the
async fn main
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.
Would you prefer it this way, or okay with how it is now? Thanks for the tip :)
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.
for me, it is fine either way, with the second way you avoid just to generate a second error
error[E0752]:
main
function is not allowed to beasync
but maybe a t-compiler member will have some preference, for me there is no problem :)
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.
Awesome, thanks mate.