-
Notifications
You must be signed in to change notification settings - Fork 13.2k
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 points at nonexisting .await #113263
Fix points at nonexisting .await #113263
Conversation
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @WaffleLapkin (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 (
|
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.
This needs a test committed for it, placed somewhere in tests/ui/parser
probably, or maybe tests/ui/async-await
.
Also, I'm not sure that this is the right fix? Why did you need to remove the maybe_recover_from_bad_qpath
here? I think the only thing you need to fix is the span you pass in (lo.to(sp)
).
Nevermind, seems like the right fix is to just return an expression with the ExprKind::Err
kind always, not just on try expressions.
Marking this as waiting on author, see the comment from rustbot above to switch it back to the "waiting on review" state. @rustbot author |
3e3449b
to
9cae051
Compare
@Alef-gabriel: This PR is missing a fix, did you drop a commit by accident? Keep in mind that the original issue requires debug assertions to be enabled. |
@compiler-errors: sorry, I don't checked my commits,I misplaced the commit with this modification, but I redid it. |
The job Click to see the possible cause of the failure (guessed by this bot)
|
☔ The latest upstream changes (presumably #114756) made this pull request unmergeable. Please resolve the merge conflicts. |
@Alef-gabriel any updates on this? if you can resolve the conflicts we can push this forward for a review |
Closing this as inactive. Feel free to reöpen this pr or create a new pr if you get the time to work on this. Thanks (The issue also seems to be resolved) |
fixes: #113203