-
Notifications
You must be signed in to change notification settings - Fork 13.1k
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
Suggest adding return
if the for semi which can coerce to the fn return type
#115196
Merged
Merged
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
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
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
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
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
61 changes: 61 additions & 0 deletions
61
tests/ui/inference/issue-86094-suggest-add-return-to-coerce-ret-ty.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,61 @@ | ||
struct MyError; | ||
|
||
fn foo(x: bool) -> Result<(), MyError> { | ||
if x { | ||
Err(MyError); | ||
//~^ ERROR type annotations needed | ||
} | ||
|
||
Ok(()) | ||
} | ||
|
||
fn bar(x: bool) -> Result<(), MyError> { | ||
if x { | ||
Ok(()); | ||
//~^ ERROR type annotations needed | ||
} | ||
|
||
Ok(()) | ||
} | ||
|
||
fn baz(x: bool) -> Result<(), MyError> { | ||
//~^ ERROR mismatched types | ||
if x { | ||
1; | ||
} | ||
|
||
Err(MyError); | ||
} | ||
|
||
fn error() -> Result<(), MyError> { | ||
Err(MyError) | ||
} | ||
|
||
fn bak(x: bool) -> Result<(), MyError> { | ||
if x { | ||
//~^ ERROR mismatched types | ||
error(); | ||
} else { | ||
//~^ ERROR mismatched types | ||
error(); | ||
} | ||
} | ||
|
||
fn bad(x: bool) -> Result<(), MyError> { | ||
Err(MyError); //~ ERROR type annotations needed | ||
Ok(()) | ||
} | ||
|
||
fn with_closure<F, A, B>(_: F) -> i32 | ||
where | ||
F: FnOnce(A, B), | ||
{ | ||
0 | ||
} | ||
|
||
fn a() -> i32 { | ||
with_closure(|x: u32, y| {}); //~ ERROR type annotations needed | ||
0 | ||
} | ||
|
||
fn main() {} |
98 changes: 98 additions & 0 deletions
98
tests/ui/inference/issue-86094-suggest-add-return-to-coerce-ret-ty.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,98 @@ | ||
error[E0282]: type annotations needed | ||
--> $DIR/issue-86094-suggest-add-return-to-coerce-ret-ty.rs:5:9 | ||
| | ||
LL | Err(MyError); | ||
| ^^^ cannot infer type of the type parameter `T` declared on the enum `Result` | ||
| | ||
help: consider specifying the generic arguments | ||
| | ||
LL | Err::<T, MyError>(MyError); | ||
| ++++++++++++++ | ||
help: you might have meant to return this to infer its type parameters | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I wonder if it would make sense to just ask Just a thought 🙂 |
||
| | ||
LL | return Err(MyError); | ||
| ++++++ | ||
|
||
error[E0282]: type annotations needed | ||
--> $DIR/issue-86094-suggest-add-return-to-coerce-ret-ty.rs:14:9 | ||
| | ||
LL | Ok(()); | ||
| ^^ cannot infer type of the type parameter `E` declared on the enum `Result` | ||
| | ||
help: consider specifying the generic arguments | ||
| | ||
LL | Ok::<(), E>(()); | ||
| +++++++++ | ||
help: you might have meant to return this to infer its type parameters | ||
| | ||
LL | return Ok(()); | ||
| ++++++ | ||
|
||
error[E0308]: mismatched types | ||
--> $DIR/issue-86094-suggest-add-return-to-coerce-ret-ty.rs:21:20 | ||
| | ||
LL | fn baz(x: bool) -> Result<(), MyError> { | ||
| --- ^^^^^^^^^^^^^^^^^^^ expected `Result<(), MyError>`, found `()` | ||
| | | ||
| implicitly returns `()` as its body has no tail or `return` expression | ||
... | ||
LL | Err(MyError); | ||
| - help: remove this semicolon to return this value | ||
| | ||
= note: expected enum `Result<(), MyError>` | ||
found unit type `()` | ||
|
||
error[E0308]: mismatched types | ||
--> $DIR/issue-86094-suggest-add-return-to-coerce-ret-ty.rs:35:10 | ||
| | ||
LL | if x { | ||
| __________^ | ||
LL | | | ||
LL | | error(); | ||
| | - help: remove this semicolon to return this value | ||
LL | | } else { | ||
| |_____^ expected `Result<(), MyError>`, found `()` | ||
| | ||
= note: expected enum `Result<(), MyError>` | ||
found unit type `()` | ||
|
||
error[E0308]: mismatched types | ||
--> $DIR/issue-86094-suggest-add-return-to-coerce-ret-ty.rs:38:12 | ||
| | ||
LL | } else { | ||
| ____________^ | ||
LL | | | ||
LL | | error(); | ||
| | - help: remove this semicolon to return this value | ||
LL | | } | ||
| |_____^ expected `Result<(), MyError>`, found `()` | ||
| | ||
= note: expected enum `Result<(), MyError>` | ||
found unit type `()` | ||
|
||
error[E0282]: type annotations needed | ||
--> $DIR/issue-86094-suggest-add-return-to-coerce-ret-ty.rs:45:5 | ||
| | ||
LL | Err(MyError); | ||
| ^^^ cannot infer type of the type parameter `T` declared on the enum `Result` | ||
| | ||
help: consider specifying the generic arguments | ||
| | ||
LL | Err::<T, MyError>(MyError); | ||
| ++++++++++++++ | ||
|
||
error[E0282]: type annotations needed | ||
--> $DIR/issue-86094-suggest-add-return-to-coerce-ret-ty.rs:57:27 | ||
| | ||
LL | with_closure(|x: u32, y| {}); | ||
| ^ | ||
| | ||
help: consider giving this closure parameter an explicit type | ||
| | ||
LL | with_closure(|x: u32, y: /* Type */| {}); | ||
| ++++++++++++ | ||
|
||
error: aborting due to 7 previous errors | ||
|
||
Some errors have detailed explanations: E0282, E0308. | ||
For more information about an error, try `rustc --explain E0282`. |
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
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.
@estebank
I fixed the conflicts, please have a review.
this changed because of this commit:
91b9ffe
I need to clone
span
andcause code
from errors forcollect_unused_stmts_for_coerce_return_ty
.Any better solution?
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 what's going on,
report_fulfillment_errors
now takes ownership, a change I made purely because we never needed access to the errors after reporting before this change.Would it be feasible to instead modify the error cause code to carry an
Option<Span>
for the place where thereturn
would be suggested? That way we don't need to leverage the "steal" mechanism nor clone the errors only iterate over them. We do something similar for errors coming from type parameters or from function arguments.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.
Do you mean to add a field
Option<span>
toExprBindingObligation
, then useObligationCause
'smap_code
API to update the trigger span?I tried this solution and seems involve a wider change, and end with that we can not get the
diag
here if we don't use the "steal" mechanism:rust/compiler/rustc_hir_typeck/src/fn_ctxt/checks.rs
Line 1889 in 25d38c4