Parallel usage of rust-analyzer and bacon-ls

[michaelrommel]

Dear Matteo,

in your Readme, you explained, that rust-analyzer's diagnostics and check on save shall be deactivated. Can you explain a bit why this is needed? I tried it in a simple project with on source file and there was not a problem. rust-analyzer provides simplified diagnostics even before save, so that is a boon for me. I wonder, where I would run into difficulties, though...

If I enable both, I get all diagnostics from both parties - what am I possibly missing here? Isn't using bacon-ls basically the same as running bacon alongside neovim in another terminal window? It is just the reading of bacon's diagnostics file and exposing it as a second language server, isn't it?

Thanks for your insights!

[crisidev]

Hello Michael,
the reason behind suggesting to disable rust-analyzer diagnostics is purely about speed. rust-analyzer is known to be pretty slow in generating diagnostics for large repositories. It is not strictly required to disable RA diagnostics, but bacon-ls was developed to just overcome this speed issue, hence the suggestion. Both LSP server can work together nicely, as you noticed, it's up to you if you want to keep them both!

[michaelrommel]

Thank you for the explanation! I guess as I am a Rust beginner, it will take some time until I reach the point, where the speed may be a concern for me. I'll keep this in mind and see how the landscape of tools evolves until then. Thanks for exposing bacon hints in neovim! I appreciate that very much!

Cheers, Michael.