Yes, nimlsp uses nimsuggest as a library creating multiple objects with 
compiler state instead of multiple nimsuggest instances. The downside is that 
nimsuggest crashes also kills nimlsp. However with any decent LSP client this 
shouldn't be much of an issue as it will simply get restarted. Hopefully it 
will also lead to fewer nimsuggest bugs, but I've yet to see a huge improvement 
yet.

Reply via email to