-
Notifications
You must be signed in to change notification settings - Fork 13.3k
fix: improve error messaging for unreachable loop return cases #119178
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
fix: improve error messaging for unreachable loop return cases #119178
Conversation
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @b-naber (or someone else) soon. Please see the contribution instructions for more information. Namely, in order to ensure the minimum review times lag, PR authors and assigned reviewers should ensure that the review label (
|
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
e282c43
to
3b99407
Compare
@rustbot review |
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.
Could you please add a test for this in tests/ui
?
ok! |
r? fmease |
@yossydev any updates on adding the test? thanks |
We are currently making it! Is it possible to wait a little longer...? |
@yossydev sure take your time, just wanted to check if you were still working on it or if there some issue that we can help resolve. Thanks |
@yossydev I'd say enough time has passed, I'll close this PR due to inactivity. Feel to free to open a new PR once you find the time to work on this again. You can also ping me if and before you'd like to push your changes to this PR since I think I need to reopen it for you (?). Note that the next time around it would be great if you could add some sort of UI test as well as a short explainer how the changes relate to issue #116572 (if it works towards fixing it, if it fixes it completely, ...). You can consult the rustc dev guide on writing UI tests and a lot of other things. |
Check to see if the pattern is single binding, and if so, display a better error message!
ref: #116572