-
Notifications
You must be signed in to change notification settings - Fork 12.5k
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
[type error] when wrongly destructing boxes of ints #105946
Comments
without #![feature(half_open_range_patterns_in_slices)]
fn main() {
let [_y..] = [Box::new(1), Box::new(2)];
} |
another one fn digit() -> str {
return {};
}
|
What ideal output would you suggest? Should we remove the suggestion line like:
|
Ideally we should be checking that the return type is suggestable. If it's not suggestable, don't mention it. |
@rustbot claim |
I actually believe that neither the E0029 nor the E0277 should have been emitted. I would check explicitly for |
The PR #106499 will prevent E0029 and E0277 from printing out after checking the type references. |
…ebank fix [type error] for error E0029 and E0277 check explicitly for the type references error if ty.references_error() is true change the error to be err.delay_as_bug() and prevent the error E0029 and E0277 from emitting out this fix rust-lang#105946
Given the following code:
The current output is:
We shouldn't show
[type error]
here.The text was updated successfully, but these errors were encountered: