Astro Hacker News - Show HN: Create a full language server in Go with 3.17 spec support

bbkane |next [-]

Started in case I ever build a language server, thanks! The interface looks very understandable, and the debug server looks really nice.

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 ..)

0: https://github.com/bbkane/warg

rumno0 |root |parent [-]

I wrote this for the infracost LSP so I could write multiple IDE extensions. Its not even really a language server, its just a neat way to parse the Terraform/Cloudformation and return diagnostics.

Language servers are cool!

Myzel394 |next |previous [-]

Have you tried out https://github.com/tliron/glsp?

rumno0 |root |parent [-]

I actually started out using that. I wanted a debug UI to track messages which was the major driver in creating my own tbh

SwiftyBug |next |previous [-]

Very nice. Now I want to build a language server. If only I had anything to build it for.

catlifeonmars |root |parent |next [-]

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.

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.

Lots of neat editor-independent interactions can be enabled using language servers.

rumno0 |root |parent |previous [-]

thanks!

Thankfully, I finally had a reason to build an LSP (infracost LSP), so it motivated this and I'm really pleased with it

peaklineops |next |previous [-]

[dead]

zephyrwhimsy |next |previous [-]

[dead]

devnotes77 |next |previous [-]

[dead]

zephyrwhimsy |next |previous [-]

Markdown survived because it optimized for the right tradeoff: human readability with just enough structure for machine parsing.

whateveracct |previous [-]

   // DiagnosticSeverity indicates the severity of a diagnostic.
   type DiagnosticSeverity int

Hmmm :robot:

jryio |root |parent |next [-]

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

rumno0 |root |parent |previous [-]

Yeah some times godoc comments look crap by necessity

fainpul |root |parent [-]

But you don't have to add a docstring. Cases like this are worse than no docstring at all, because it wastes the reader's time.

If you add one, at least make the effort to provide some useful information. For example which is more severe: higher or lower numbers.

rumno0 |root |parent |next [-]

I disagree - you should have docstring and I don't think this is worse by having it... its just not ideal

hrmtst93837 |root |parent |previous [-]

Boilerplate docstrings are lint that spreads, and stale ones are worse, I've seen sevreity fields documented less clearly than the code they annotate.