-
-
Notifications
You must be signed in to change notification settings - Fork 190
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Language Server support #567
Comments
C3 used to have an AST printer, but such a format was more informative than intended for LSPs. It's also the concern that the AST is sometimes rewriting things from the concrete tree and as such might not correctly match the LSP output. But a starting point should probably be trying to create a LSP-format AST printing function. |
The error can then be taken from the --test output. Create a --lsp mode similar to --test |
|
After some reflexion, we should probably not use |
Atfer discord discussion, the |
What's the state of this? |
Hi @lerno, i should have a branch somewhere with basic communication using lsp protocol. |
Just found it : https://github.com/jb-perrier/c3c/tree/lsp |
I'm looking forward to it! |
Hi, any news on this? 👀 |
Unfortunately no, i was just stuck to an issue i wasn't able to fix for some reason. I had to switch to other things. |
Do you know what issue that was? |
FYI there's a WIP language server implementation at https://github.com/pherrymason/c3-lsp. It was recently updated with the stdlib for 0.6.0. |
Should we close this now? Given that there is a separate lsp? |
Having a language server for all famous IDE is a key step for spreading C3 into the programming world.
This issue will enable us to track the needs, how it can be done and anything related to this subject.
For now,
--test
mode enable us to get error reports, in order to have auto completion and any feature AST related we need to access the AST generated in parsing part of c3c.Few solutions comes to my mind rn:
Feels free to express your ideas below.
The text was updated successfully, but these errors were encountered: