Unable to install extension 'matklad.rust-analyzer' as it is not compatible with VS Code '1.51.1'.
Why are we bumping the VS Code requirement so aggressively? NixOS is still on 1.51.1, so using rust-analyzer master is impossible there.
We used to support only the latest version, but now that's supposed to be the latest two versions
Hm, good call on the latest two versions
guess it makes sense to revert that on the reelase branch...
Hm, thinking just a bit more about it, seems like "two releases" strategy is not tenable... cc @Jeremy Kolb .
The problem is that the underlying LSP library we use uses "latest stable" policy. This is understandable -- they need to bind to the latest VS Code APIs to use new features. And we need to use the latest library to have access to latest features as well. Sticking to an older release is not an option imo: supporting older vscodes is good, but enforcing older vscodes on everyone is not.
I think the simplest thing we can do is reverting to the "latest stable" policy, + a provision that old extensions work with new server binary
(which, sadly, isn't the case in today's release)
Some alternatives are:
I'm not sure how to solve the
vscode-languageclient versioning. We could stick with the latest stable package but then we'd be missing out on things like semantic highlighting for 9 months so I'm not a big fan of that option.
I think it may make sense to have some sort of extension/server compatibility matrix
I think the "doesn't die on startup" would be good enough level of compat
ah, that's probably rust-analyzer#6979 then as well...
... or at least related to that?
:( :( :(
that's me messing-up release
Hm, can anyone spot the bug in https://github.com/gluon-lang/lsp-types/pull/193/files ?
It looks right...
The existing code is wrong. According to the spec it needs to be
That might be causing deserialize to fail
Is https://github.com/rust-analyzer/rust-analyzer/issues/6414#issuecomment-749063940 the same problem?