KotlinLanguageServer VS rust-analyzer

There's a community-made one, but of course as much effort as has been put into it it's not as featureful as JetBrains's own stuff.

Kotlin is probably the worst case for Neovim. While there is a language server for Kotlin, it's not very advanced and does not look like it's actively developed.

Hi, if you are going to do Kotlin the easiest choice is android studio with Kotlin plugin. Using Vscode is more tricky because Jetbrains does not want to support lsp for Kotlin so you only have https://github.com/fwcd/kotlin-language-server available to write Kotlin on Vscode.

Kotlin Language Server puts a warning on this code, because the bar inside the lambda shadows the function argument bar. Flow typing solves this problem by eliminating the need to redefine bar as a new non-nullable variable in the branch where we've verified it's non-nullable.

You want to change something about that? Go and help over at the kotin lsp server. It's maintained, and welcomes contributions. I sometimes use it in my day job (writing Kotlin backend code)

There is https://github.com/fwcd/kotlin-language-server, but I wouldn't expect something more official from a company that refuse to support LSP in their IDEs. JetBrains is the Apple of the IDE world.

Oddly enough, we use mostly the same languages. However, I would advise against using neovim with Kotlin: its language server has an excessive memory usage and its debugger is cumbersome with neovim (I haven't managed to get it working, and currently it also lacks an entry in nvim-dap's wiki).

I'll bring up the Kotlin LSP[0] every time I see Kotlin on HN because I really hope the LSP takes off (which would make it viable to use Kotlin with a non-IntelliJ editor).

Kotlin as a language looks really cool, but I don't want to give up terminal-based, modal editing (which I'd have to in order to use IntelliJ).

Along those lines, I once tried diving into using Gradle outside IntelliJ, and I couldn't find any good resources to help with that. If folks have hints/links-to-blog-posts with regards to that as well, that'd be great!

[0] https://github.com/fwcd/kotlin-language-server#this-reposito...

I've tried [this Kotlin LSP](https://github.com/fwcd/kotlin-language-server) and it isn't perfect. It's not complete, but it does some of the basic things.

I've downloaded kotlin language server from here: https://github.com/fwcd/kotlin-language-server

#14561 map tokens from include! expansion to the included file

return { tools = { -- autoSetHints = false, on_initialized = function() vim.api.nvim_create_autocmd({ "BufWritePost", "BufEnter", "CursorHold", "InsertLeave" }, { pattern = { "*.rs" }, callback = function() vim.lsp.codelens.refresh() end, }) end, auto = false, inlay_hints = { -- Only show inlay hints for the current line only_current_line = false, auto = false, -- Event which triggers a refersh of the inlay hints. -- You can make this "CursorMoved" or "CursorMoved,CursorMovedI" but -- not that this may cause higher CPU usage. -- This option is only respected when only_current_line and -- autoSetHints both are true. only_current_line_autocmd = "CursorHold", -- whether to show parameter hints with the inlay hints or not -- default: true show_parameter_hints = false, -- whether to show variable name before type hints with the inlay hints or not -- default: false show_variable_name = false, -- prefix for parameter hints -- default: "<-" -- parameter_hints_prefix = "<- ", parameter_hints_prefix = " ", -- prefix for all the other hints (type, chaining) -- default: "=>" -- other_hints_prefix = "=> ", other_hints_prefix = " ", -- whether to align to the lenght of the longest line in the file max_len_align = false, -- padding from the left if max_len_align is true max_len_align_padding = 1, -- whether to align to the extreme right or not right_align = false, -- padding from the right if right_align is true right_align_padding = 7, -- The color of the hints highlight = "Comment", }, hover_actions = { auto_focus = false, border = "rounded", width = 60, -- height = 30, }, }, server = { --[[ $ mkdir -p ~/.local/bin $ curl -L https://github.com/rust-analyzer/rust-analyzer/releases/latest/download/rust-analyzer-x86_64-unknown-linux-gnu.gz | gunzip -c - > ~/.local/bin/rust-analyzer $ chmod +x ~/.local/bin/rust-analyzer --]] -- cmd = { os.getenv "HOME" .. "/.local/bin/rust-analyzer" }, cmd = { os.getenv "HOME" .. "~/.cargo/bin/rust-analyzer" }, on_attach = require("user.lsp.handlers").on_attach, capabilities = require("user.lsp.handlers").capabilities, settings = { ["rust-analyzer"] = { lens = { enable = true, }, checkOnSave = { command = "clippy", }, }, }, }, }

I would like changes like https://github.com/rust-analyzer/rust-analyzer/pull/13799 to be listed in 'Breaking Changes' category, to приманка draw the users' attention.

For those of you who haven’t heard of Mun before, Mun is an embeddable programming language empowering creation through iteration. The idea to create Mun originated out of frustration with the Lua dynamic scripting language and a desire to have similar hot reloading functionality available in Rust. As such, it’s not a direct competitor with Rust, but instead is intended to be used with Rust (or C/C++) as a host/embedded language pairing. Actually, Mun is completely written in Rust, building on similar crates as rust-analyzer and rustc. Its key features include:

#13728 upgrade chalk to make solver fuel work again (works around most trait solving hangs).

#13221 (first contribution) add option to move lenses above doc comments (rust-analyzer.lens.location):

Rust-analyzer has a good overview: https://github.com/rust-analyzer/rust-analyzer/blob/master/docs/dev/syntax.md

#12517 (first contribution) fix completion for methods in trait generated by macro.

-- all the opts to send to nvim-lspconfig -- these override the defaults set by rust-tools.nvim -- see https://github.com/neovim/nvim-lspconfig/blob/master/doc/server_configurations.md#rust_analyzer server = { -- on_attach is a callback called when the language server attachs to the buffer -- on_attach = on_attach, settings = { -- to enable rust-analyzer settings visit: -- https://github.com/rust-analyzer/rust-analyzer/blob/master/docs/user/generated_config.adoc ["rust-analyzer"] = { -- enable clippy on save checkOnSave = { command = "clippy" }, assist = { importGranularity = "module", importPrefix = "self", }, cargo = { loadOutDirsFromCheck = true }, procMacro = { enable = true }, } } },

#12349 publish universal VSIX to make Code happy.