Started in case I ever build a language server, thanks! The interface looks very understandable, and the debug server looks really nice.<p>Now that I think about it, it might be really cool to add LSP to my CLI framework[0] (I already have tab completion for shells, why not make an editor plugin if it's this easy ..)<p>0: <a href="https://github.com/bbkane/warg" rel="nofollow">https://github.com/bbkane/warg</a>
Have you tried out <a href="https://github.com/tliron/glsp" rel="nofollow">https://github.com/tliron/glsp</a>?
Markdown survived because it optimized for the right tradeoff: human readability with just enough structure for machine parsing.
Very nice. Now I want to build a language server. If only I had anything to build it for.
To give you some idea how versatile a language server is, I wrote one once to provide go-to-definition between two related blocks in a large proprietary YAML configuration file. If the definition was missing, it would also render the red squiggly line to indicate that something was misspelled.<p>Another time I used one to make the hosts in my SSH configuration file clickable to either open a terminal with a session or just to display cpu/memory statistics.<p>Lots of neat editor-independent interactions can be enabled using language servers.
thanks!<p>Thankfully, I finally had a reason to build an LSP (infracost LSP), so it motivated this and I'm really pleased with it
[dead]
[dead]
[dead]
<p><pre><code> // DiagnosticSeverity indicates the severity of a diagnostic.
type DiagnosticSeverity int
</code></pre>
Hmmm :robot:
The godoc format enforces that the comment start with the name of the identifier and be a complete sentence(s) describing what that identifier does. Predates LLMs
Yeah some times godoc comments look crap by necessity
But you don't <i>have to</i> add a docstring. Cases like this are worse than no docstring at all, because it wastes the reader's time.<p>If you add one, at least make the effort to provide some useful information. For example which is more severe: higher or lower numbers.
Boilerplate docstrings are lint that spreads, and stale ones are worse, I've seen sevreity fields documented less clearly than the code they annotate.
I disagree - you should have docstring and I don't think this is worse by having it... its just not ideal