Closed MahdiBM closed 11 months ago
Tracked in Apple’s issue tracker as rdar://114864256
sourcekit-lsp should report the secondary symbols returned by the sourcekitd cursor info response.
@ahoppen I assume that's just a note tracking the progress of the issue? Or do I need to do something? 🙂
Oh, no, that’s just a note of what we should do to fix this.
Consider this code:
Using VSCode with SSWG Swift extension, in
value.doThing()
, when you right click ondoThing()
to jump to definition, it'll just automatically jump to the protocol. This seems to be a SourceKit-LSP limitation.Xcode/sourcekitd though is more smart about it and lets you choose between the protocol or one of the implementations: