-
Notifications
You must be signed in to change notification settings - Fork 790
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 design proposal #16493
LSP design proposal #16493
Conversation
✅ No release notes required |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Left some very early thoughts. We should probably have a chat between the F# team and the FSAC maintainers about how things will work together.
Would this move FCS to something higher than |
We still have to target |
Not at this point. Once we are fully out of process, we can think about it. |
Library on top of lsp will be net9 likely. |
To add, given that long-term we want to:
Once done, we can probably move to latest (-ish) target for FCS, so we can utilise things like Spans, and vectorized collection operations, etc. |
What are the initial thoughts on the release process for these LSP deliverables? |
That is to be decided, didn't really think about it yet. |
Co-authored-by: Vlad Zarytovskii <vzaritovsky@hotmail.com>
Co-authored-by: Vlad Zarytovskii <vzaritovsky@hotmail.com>
This is a design document for F# LSP. It's not exhaustive and definitely not final, but should be good to kick start discussions about the topic and base some initial work/investigation off of.
Please check it out and comment/suggest changes and point out missing parts.
To view rendered markdown go to Files changed,
...
-> View file