5 ms·
What’s the LSP and linter/formatter story these days? Last time I tried it the lsp was miles behind what I am used to from TypeScript land in vscode. I have got
by Escapado 4y ago
What’s the LSP and linter/formatter story these days? Last time I tried it the lsp was miles behind what I am used to from TypeScript land in vscode. I have gotten sooo used to all the auto completion, helpful error tooltips and auto imports and formatting on save that it felt tedious not to have that in a similar capacity. Maybe I was just doing things wrong and it’s been a while. In general I am super intrigued by nim coming from python originally. I wish I could use it professionally on a project just to spend more time with it
- elcritch 4y agoIts ok. A developer was recently hired to work on it full time though!
- zelphirkalt 4y agoOn it or with it?
- elcritch 4y agoOn it, to improve the lsp tooling.
- j-james 4y agoIt's alright when it doesn't crash. But it frequently crashes. Tooling is definitely a weakness of Nim (although it's improving). More specifically: right now auto completion is excellent, implicit type annotations are excellent, error tooltips on save work, broader rename/refactor support is limited/nonexistent, formatting on save is fine, auto imports don't exist (and probably shouldn't given that it's typical to use unqualified namespaces).