tree-sitter-rust VS LanguageClient-neovim

Yes. It's typically a fair bit slower than a hand-coded parser. The idea sounds great until you're working on a codebase with 2 million LOC. At that point, the speed of a cold parse is most important, whereas TS is designed for fast re-parsing of a single file. These aren't great numbers but the Rust TS parser is reportedly 2x slower than rustc's https://github.com/tree-sitter/tree-sitter-rust. It's no surprise that you just use the faster option if it's convenient.

Notes for anyone interested, there is this PR https://github.com/tree-sitter/tree-sitter-rust/pull/128, which merges successive doc comments.

Tree-sitter is a fantastic parser generation and incremental parsing library, that supports Rust language bindings and has an available parser Rust tree-sitter-rust.

You can see a much more in-depth version at https://github.com/tree-sitter/tree-sitter-typescript or https://github.com/tree-sitter/tree-sitter-rust

I'll be really interested to see what folks end up preferring once nvim 0.5 ships with treesitter support. Do folks have any experience with the Rust grammar?

Neovim comes with a client. For Vim you will need to install one, such as CoC, LanguageClient-neovim, or vim-lsp.

i know the language client neovim has such a function (:help languageclient_textdocument_codelens after compiling its helptags). AFAIK you can get that running in Vim 8, but not sure.

On NeoVim, the built-in LSP client works without modification. On Vim, you will need LanguageClient-neovim.

I'm using LanguageClient-neovim. Here's the relevant portions of my init.vim:

I just saw a nice post in /u/medwatt about using vim for VHDL/Verilog and thought I'd contribute a little! * Syntax and error highlight: https://github.com/autozimu/LanguageClient-neovim * Column align: https://github.com/junegunn/vim-easy-align * Remove annoying whitespaces: https://github.com/ntpeters/vim-better-whitespace * Partial (fuzzy) filename search: https://github.com/junegunn/fzf.vim * Outline all declarations inside a file: ⠀https://github.com/preservim/tagbar * Treat indentations as vim-objects (useful for languages that don't use { }): https://github.com/michaeljsmith/vim-indent-object There is also mouse support in vim for those who want it. Try typing :set mouse=a. Very useful for resizing windows. I also highly recommend you get good at using folds (https://vim.fandom.com/wiki/Folding). It makes it a LOT easier to navigate files. You can save your fold config per-file with :mkview and load it later with :loadview. If I come up with more hints - I'll mention them in the comments!

I've been using LanguageClient and solargraph gem with plain Vim 8 for a long time already. Still, having a bit better experience at Ruby coding with Emacs and its lsp-mode & company & inf-ruby combo.

Might migrate to Neovim's native LSP support at some point, however I find vim-lsp more feature complete out of the box. I used to use LanguageClient-neovim, however, I missed proper support for signature help.

YCM is a client. The client is a plugin for Vim or Neovim, even the "built-in" client in Neovim is just a Lua plugin that is included with the editor, it's not really built-in. Examples of other clients:LanguageClient-neovim, vim-lsp, ale.

LanguageClient-neovim just merged some support for semantic tokens and the plan, as I read the PR/issues, is to next implement some default mappings from the semantic tokens to highlight groups.