-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Support Question Mark Operator in Control Flow Highlighting #18147
Labels
C-feature
Category: feature request
Comments
That is really really weird... We have code for highlighting when on |
That sounds plausible at least. |
This is a known VSCode issue |
Duplicate of #9395 |
bors
added a commit
that referenced
this issue
Oct 14, 2024
…kril feat: Highlight exit points of async blocks Async blocks act similar to async functions in that the await keywords are related, but also act like functions where the exit points are related. Fixes #18147
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
rust-analyzer can nicely highlight which control flow relevant pieces of the code relate to each other, such as shown here:
This currently does not extend to the question mark operator:
However, while writing this issue, I did notice that it actually works perfectly fine already if you are on the
fn
itself:The text was updated successfully, but these errors were encountered: