-
Notifications
You must be signed in to change notification settings - Fork 3
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
LSP #3
Comments
same here. |
Thank you in advance! I'll also try to learn LSP, but I'll write drafts when I can get my hands on my dev PC |
Wait, I just realized, we'll have to delay the LSP, because of Rick-Lang/rickroll-lang#76, as the Rust implementation might end up being a slightly different language |
You are right. Also I am very sorry that I don't have time to maintain this language regularly. |
omg i completely forgot about the LSP 😭 |
Don't worry, I've been (and still am) busy 😅
Me too, lol |
I'll be honest, I have no idea how to write an LSP 💀. But this would benefit RR, for the same reason as LLVM.
The extension would act as a "bridge" (interface) between VSC and RR-LSP, which is how
rust-analyzer
and Golang-ext work (please, anyone, correct me if I'm wrong). So the extension would still exist, but now we'll have an "universal" API that other code-editors (such ashx
, and NVim) could useThe text was updated successfully, but these errors were encountered: