You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Massive thanks for landing the fancy new inlay hints! 🧡
I have been a big fan of the inlay hints for a long while, and I use them all the time. That's also why I noticed a small regression in the feature and am hoping this is something that can be easily fixed.
Previously, the inlay hints themselves were hoverable to get an information box of the type that was inlaid. Additionally, holding cmd while hovering it provided additional information - similar to hovering any actual variable instances.
Currently, with the new inlay hint version, there's no information box given when you hover an inlay hint.
In some cases, it is possible to move the cursor to a nearby variable which holds the instance of the type, but this is less convenient. For example sometimes in pattern matching cases, the variable may be very small (one letter) compared to the inlay hint, which will have the full name displayed.
Additionally, in some cases such as method chaining, the inlay hints very helpfully show the intermediate types during the chain, but you won't have the actual variables available for hover tooltips at all.
It would be great to have the hover-ability back for the inlay hints. I hope this is possible to fix within the new inlay hint api.
I was very confused because this was never a thing, but I just realized hovering the decorator was like hovering the identifier next to it (or the expression for chains) for which we do gave away the type in the hover 😅 So ye technically thats a regression.
This would be part of #11701 where we can actually make every segment hoverable on its own.
Massive thanks for landing the fancy new inlay hints! 🧡
I have been a big fan of the inlay hints for a long while, and I use them all the time. That's also why I noticed a small regression in the feature and am hoping this is something that can be easily fixed.
Previously, the inlay hints themselves were hoverable to get an information box of the type that was inlaid. Additionally, holding
cmd
while hovering it provided additional information - similar to hovering any actual variable instances.Currently, with the new inlay hint version, there's no information box given when you hover an inlay hint.
In some cases, it is possible to move the cursor to a nearby variable which holds the instance of the type, but this is less convenient. For example sometimes in pattern matching cases, the variable may be very small (one letter) compared to the inlay hint, which will have the full name displayed.
Additionally, in some cases such as method chaining, the inlay hints very helpfully show the intermediate types during the chain, but you won't have the actual variables available for hover tooltips at all.
It would be great to have the hover-ability back for the inlay hints. I hope this is possible to fix within the new inlay hint api.
Thanks for all your hard work!
Context:
VSCode Version:
1.65.2 (Universal)
VSCODE Commit:
c722ca6c7eed3d7987c0d5c3df5c45f6b15e77d1
rust-analyzer version:
v0.2.975
The text was updated successfully, but these errors were encountered: