Danny Tuppeny
Danny Tuppeny
Great, glad it was an easy fix and thanks for the test case :-)
Since it's a different stack trace to those other errors, let's keep this one open for now to ensure both issues get fixed.
Personally, I would prefer us to never "redirect" Go-to-Definition. I think if there are additional locations to return, we should return _all_ of them, and just put the one we...
> I've already tested that flow by using an analyzer_plugin and contributing custom definitions myself. > IMO that was a horrible experience. I'm not sure I follow. I posted a...
> Are you saying that this option would allow jumping to the annotated code by default. And folks could opt out by enabling the "peek" view, so that they'd see...
For VS Code/LSP I think it would be good to have semantic token modifiers on them for users to style them. I'm not yet sure if I'd prefer them greyed...
> I don't see any `SemanticTokenTypes` values that appear to be appropriate, so I was assuming that it would be a custom non-binding modifier. Yep, that's what I had in...
@pq is this something you're looking at? If not, I'm happy to add it.
I started looking at this and have a new custom modifier "wildcard" applied to variable declarations that are wildcards. However while writing tests I found that existing wildcard assignments like:...
> The inconsistency of not highlighting it bothers me, but I can't think of a good alternative at the moment. The current options I can come up with are: 1....