Daniel Sokil

@lukepighetti From what I understand, here is what features [Semantic Tokens](https://code.visualstudio.com/api/language-extensions/semantic-highlight-guide) allow. Since the Mint parser fully understands what mint code does, all we have to do is specify what...

This also fixes the issues we currently have where the render function could be defined multiple ways: ```mint fun render {} fun render: Html {} fun render { if (clicked)...

We do not have any documentation, but the existing work is being done the [language-server branch](https://github.com/mint-lang/mint/tree/language-server)

@lukepighetti You probably already know about this, but I realized a simple way to views changes specific to the language server, using GitHub compare feature: https://github.com/mint-lang/mint/compare/language-server

It would probably be easier if a binary was built from the `language-server` branch, and we could simply download it in the extension.

> I'll have to claim ignorance on the best practices there, do you have any examples or docs I can refer to so I can educate myself further? > >...

Additional Reference, Upcoming LSP Version 3.16 Specification with Semantic Tokens Support: https://microsoft.github.io/language-server-protocol/specifications/specification-3-16/

It would be great to have correct getting started instructions.

https://github.com/swoole/swoole-src Is a good idea too, speaking of PHP

@nhooyr Great!, We are using the lib in prod, thanks for your work.