Saem Ghani

In regards to the points raised in this thread: * Repeated `let ... in` vs `let ... $SEPARATOR ... in` The latter reads more nicely than the former (pure opinion),...

In regards to the question about `where` raised by @yurrriq's, a long debate has been going on in Elm, and there is a particularly [good summary of it by Colin...

I've been poking at the LSP code and trying various experiments and have found the following things that would help in general for a bit more robustness of the server,...

@bung87 I'm actually looking at the language server because I'd like to move as much as possible into one from the existing extensions. Mostly inspired by what the Haxe community...

@PMunch please see [section 4 and 4.1](https://www.jsonrpc.org/specification#request_object), by definition the id field most not be present for a notification request, this is precisely in spec for json-rpc 2.0. The indentation...

In regards to crashes, I agree that nimsuggest should have fixes against it but it's a matter of practicality. The number of folks who can implement such a fix and...

> Why do you want to do that? The entire point of LSP is to move code out of existing extensions into a single extension that everyone can help maintain...

Just having a think and I don't believe removing allow extra is necessarily the correct fix, probably a subtle violation of the LSP spec. Specifically, except for the id field...

> Are they? As far as I can tell from the specification you aren't allowed to add your own fields (apart from a couple positions that takes arbitrary objects). I...

I'll double check in my Nim port of my extension soon, but I might have inadvertantly fixed the issue and if so can perhaps she'd some light on it. (fingers...