diagnostics: suggest type annotation for closure params on HRTB FnOnce mismatch#158701
Open
Rohan-Singla wants to merge 3 commits into
Open
diagnostics: suggest type annotation for closure params on HRTB FnOnce mismatch#158701Rohan-Singla wants to merge 3 commits into
Rohan-Singla wants to merge 3 commits into
Conversation
Collaborator
|
r? @mejrs rustbot has assigned @mejrs. Use Why was this reviewer chosen?The reviewer was selected based on:
|
This comment has been minimized.
This comment has been minimized.
Collaborator
|
The job Click to see the possible cause of the failure (guessed by this bot) |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes #158393
Problem
When a closure passed to a function requiring
for<'a> FnOnce(&'a mut [u8])hasunannotated parameters (e.g.
|buf|), the compiler emits the confusing error:without explaining how to fix it.
In many cases, simply adding an explicit type annotation to the closure
parameter (e.g.
|buf: &mut [u8]|) resolves the lifetime ambiguity, but thecompiler does not currently provide any guidance.
What
This PR adds a diagnostic suggestion in
placeholder_error.rsthat detectswhen:
FnOnce,FnMut, orFn)When these conditions are met, the compiler now emits the following help
message:
Testing
A UI test has been added covering the exact reproduction case from the
reported issue.