Nick Hu
> @levincoolxyz I coded up a similar experiment, using a double buffer for input, xor'ing it together, and then compressing the result with lz4 - unfortunately, it doesn't seem any...
A simpler solution if you are content with rust stable is to just use the version of rust-analyzer from nixpkgs like so: ```nix mkShell { buildInputs = [ rust-analyzer #...
I also noticed that adding `"rust-std"` to `extensions` has no effect, as it's included by default - however, oddly enough, nix thinks it's a new derivation and you end up...
I believe the CI failures are completely unrelated to the PR
@ABorgna ping This is a very minor (and hopefully uncontroversial) change
Ah, I hadn't taken that into account, you're right that it's a breaking change in this way (but I'm pretty sure it should always be fixable by adding more typing...
@ABorgna I've updated the tests to make them pass
Whoops, I ran the extended test suite this time, so should be good now, sorry @ABorgna
You can do this manually by storing node indices as weights in the original graph, possibly tupled with any other node weight data required
I think you also want to change https://github.com/nvim-lua/completion-nvim/blob/bd4f21f35e1b6d6f4a79ff4bb8a89d812bd912a0/lua/completion.lua#L110 to ```lua if next(item.additionalTextEdits) then ``` This handles the subtle case when `item.additionalTextEdits` is `{}`, because `if {} then x else y...