Indexing doesn't appear to be working on Windows

[adam-fowler]

This bug has been triggered by the following bug in the vscode-swift repo swiftlang/vscode-swift#479.

In most cases sourcekit-lsp returns no results when asking to jump to definition for a symbol outside the current file.
The only situation I can get it to return a result is run swift package clean and then a swift build. As soon as I restart VSCode though it stops working again.

[ahoppen]

rdar://106995873

[ahoppen]

@compnerd Do you have an idea what might be going wrong here?

[compnerd]

@ahoppen completely wild guess, when we restart, we are passing a path somewhere, and the path is not being formed using the proper path component separator, i.e. / is being used somewhere rather than \.

[adam-fowler]

@ahoppen completely wild guess, when we restart, we are passing a path somewhere, and the path is not being formed using the proper path component separator, i.e. / is being used somewhere rather than \.

I had a quick check to see if vscode is passing / instead of \ and it doesn't look like it does. Most of the paths sent are URIs anyway which will use /. There is only one raw path (rootPath in the initialise) and that uses \.

[compnerd]

For some reason, I seem to remember something along the lines of the path separator being an issue because it mismatched between SPM and LSP. This resulted in the files being treated differently, which was rather annoying.

[adam-fowler]

I have this working now, the situations where I haven't are probably related to #752