feat: inlay hints on try-expr - #22981
Open
A4-Tacks wants to merge 1 commit into
Open
Conversation
rustbot
added
the
S-waiting-on-review
Show try-expr inlay hints (e.g `foo()?;` -> `foo().try?;`). Similar to `inlay_hints/range_exclusive.rs` Some people complain that the `?` operation in Rust is not obvious and is easily overlooked when reading the code Although I do not agree with this viewpoint, I have opened a PR
A4-Tacks
force-pushed
the
try-expr-hints
branch
from
August 1, 2026 17:26
c901480 to
f522aba
Compare
Member
I feel like this is better served by those folks adjusting their syntax highlighting then? |
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
3 participants
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.
Show try-expr inlay hints (e.g
foo()?;->foo().try?;).Similar to
inlay_hints/range_exclusive.rsSome people complain that the
?operation in Rust is not obvious and is easily overlooked when reading the codeAlthough I do not agree with this viewpoint, I have opened a PR