-
Notifications
You must be signed in to change notification settings - Fork 12.6k
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
Too many type inside
async object must be known in this context
errors
#66445
Labels
A-async-await
Area: Async & Await
A-diagnostics
Area: Messages for errors, warnings, and lints
A-inference
Area: Type inference
AsyncAwait-Triaged
Async-await issues that have been triaged during a working group meeting.
C-bug
Category: This is a bug.
D-verbose
Diagnostics: Too much output caused by a single piece of incorrect code.
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
Comments
jonas-schievink
added
A-async-await
Area: Async & Await
A-diagnostics
Area: Messages for errors, warnings, and lints
A-inference
Area: Type inference
C-bug
Category: This is a bug.
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
labels
Nov 15, 2019
nikomatsakis
added
the
AsyncAwait-Triaged
Async-await issues that have been triaged during a working group meeting.
label
Nov 19, 2019
estebank
added
the
D-verbose
Diagnostics: Too much output caused by a single piece of incorrect code.
label
Dec 3, 2019
@rustbot claim |
@olegnn are there other changes you'd like to see here? |
estebank
added
the
E-needs-test
Call for participation: An issue has been fixed and does not reproduce, but no test has been added.
label
Dec 9, 2021
@estebank now it looks much better! However, code like this still produces the same error twice use futures::stream::*;
async fn same_error_twice() -> Vec<u8> {
once(async { 0.0 }).collect().await
}
fn main() {}
|
Current output:
I wonder if we could extend the current deduplication logic to account for expressions and look at earlier errors in method chains... |
JohnTitor
removed
the
E-needs-test
Call for participation: An issue has been fixed and does not reproduce, but no test has been added.
label
Jan 5, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
A-async-await
Area: Async & Await
A-diagnostics
Area: Messages for errors, warnings, and lints
A-inference
Area: Type inference
AsyncAwait-Triaged
Async-await issues that have been triaged during a working group meeting.
C-bug
Category: This is a bug.
D-verbose
Diagnostics: Too much output caused by a single piece of incorrect code.
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
This code (Playground)
currently produces 11 errors:
the trait bound is not satisfied
type inside async object must be known in this context
.If you add elements to vec, it will generate even more.
The text was updated successfully, but these errors were encountered: