neovim-config VS rust-analyzer

Oh, right, thank you a lot! Here is how I did it (if someone interested): https://github.com/Shatur/neovim-config/commit/03a1483ef4160838586cdc158c595eaf6612d65f

Here is how I use it.

Do don't need to use require for files in plugin folder. They will be loaded automatically. Nothing changed, this is how it worked before. You can take a look at my configuration, I also use the built-in plugin manager: https://github.com/Shatur/neovim-config

Sure, here: https://github.com/Shatur/neovim-config I do not use lazy / async loading for simplicity but I'm pretty satisfied with my startup time. My init.lua contains configuration that unrelated to any plugin and loaded first. I use plugin folder to load all my settings for plugin (each file have the corresponding name). My lua/config_utils contains my custom scripts. I also use firenvim plugin to use neovim in text fields in browser. So I do not load some plugins if I in firenvim session (statusline, bufferline, neogit, etc.)

go build 3.62s user 0.76s system 171% cpu 2.545 total

I was looking forward to parallel front-end[4], but I have not seen any improvement for these small changes.

[1]: https://github.com/rust-lang/rust-analyzer

For example, intelephense can show diagnostics in real time, there is no need to save the file to get new diagnostics. But rust-analyzer, the language server for rust, can only update diagnostics after saving the file.

6. Rust Analyzer

The rust-analyzer readme suggests you go here for support request. But even there, you'll need to provide more details to get useful help.

For example: https://github.com/rust-lang/rust-analyzer/blob/master/docs/...

> If you create an LSP, it will work best in VS Code.

Any editor can work just as well as (or even better than) VS Code.

So, apparently the reason why rust-analyzer, the LSP server for Rust does not have persistent caching is because it would make "optimizing initial passes less important".

All I want to know is: Will it have a build configuration pulldown?

I am not a Rust dev. It surely looks great.

However, from what I understand it seems to supply just a parser separate from the Rust compiler (https://github.com/rust-lang/rust-analyzer/tree/master/crate...) trying to keep up with Rust‘s development. So, in principle, it could have been just another treesitter parser plugin, too.

So, again, the LSP framework does not directly provide any magical benefit over a static parsing framework. All the semantic analysis capabilities stem from a good parser.

rust-analyzer > manual > helix > binary > rustup component add rust-analyzer