Saem Ghani

Hmm, I'd say potentially prioritize nimsuggest more aggressively or keep it the same. Then if a build or other action is initiated, ease off in sending requests to nimsuggest so...

That's a relatively straightforward PR and it should work, only issue might be one LSP is more feature complete than the other, but over time capability testing could be added...

Thanks for taking the time to raise the issue, @tanelso2. I unfortunately really don't know the syntax highlight bits of VS Code and used the existing grammar, so it's unlikely...

Is this still a bug because I can't seem to replciate it?

Just tested it with the latest version, I can't replicate the crash even with repeated calls. `nimsuggest` version: ``` Nim Compiler Version 1.5.1 [Linux: amd64] Compiled at 2021-01-03 Copyright (c)...

This might be as simple as removing the [assert](https://github.com/nim-lang/Nim/blob/dbff2cd938b326279de0f3f97b2dd8c54a90468a/compiler/semtypes.nim#L2046) or if it's required putting in a guard for nimsuggest. I wasn't able to entirely figure out the reason why the...

I can't replicate this with latest nimsuggest https://github.com/saem/nim-misc/blob/main/nimsuggest_116_chronos_error/src/main.nim (ignore the nimble cruft) nimsuggest version: ``` Nim Compiler Version 1.5.1 [Linux: amd64] Compiled at 2021-01-03 Copyright (c) 2006-2020 by Andreas Rumpf...

I don't think this is a bug, you're missing an `import strutils` at the top, as `in` is sugar for `contains`, and the particular implementation you're looking for is defined...

> https://forum.nim-lang.org/t/6862#42899 (Starting a pure Nim Vscode extension) but code archived https://github.com/saem/vscode-nim-fork @mratsim as @RSDuck pointed out the Nim extension for VS Code written in Nim is still alive: https://github.com/saem/vscode-nim....

@dom96 > I've been saying this for a while now, and will continue to say it until I successfully inspire someone to implement it: let's have a Language Server implementation...