Rudi Grinberg

Ignoring the fiber issue (we wouldn't them in the lsp library), that would only work server side. On the client side, when we make a request we know in advance...

This issue is postponed until vscode gains support for this.

I'd say this is a dune issue rather than an LSP issue. But more concretely, we should be able to address things the following way: 1. Improve `ocamlc-loc` to understand...

Merlin reuses the compiler api for printing errors so the distinction is usually a matter of flags + version differences. So we should be able to use the same api....

Directives already have documentation attached to them I think. Isn't there an easy way to view them?

It would be obviously nice to have this, but isn't there work in the compiler to provide structured type errors already? Ideally, we would just piggy back on that and...

> I'd say it's better to have only one exception with a sum type as argument (+ a printer for the sum type). Otherwise, I do like the idea a...

> I was more thinking of a closed sum type, maybe with a … | Custom of {msg: string} or something like that, so that jsonrpc error codes are always...

Do you think that the object oriented code poses such a block for OCaml programmers? Most programmers are already familiar with OO from other languages and it really isn't all...

Note that this branch needs the code generation stuff to be merged before it’s revived. We will be able to generate the class definition as well