-
Notifications
You must be signed in to change notification settings - Fork 53
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
Mono-repoize Calyx LSP + Tree-sitter #1922
Conversation
|
||
[dependencies.tokio] | ||
version = "1" | ||
features = ["io-util", "io-std", "macros", "rt-multi-thread", "net"] |
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.
Multi-threading! In 2024!!
Looks awesome! I will ask you to document things to your discretion so we can fix breakages when they happen. It might be good to provide a high-level overview in the |
(very preliminary implementation)
I think that this is at a point where it's ready to review / merge into main. I've setup package publishing for the VSCode extension so that it's installable from the VSCode store. In the future it would be nice if it good automatically install the |
AMAZING. I looked things over briefly and I think everything's good to go! I don't know much about the crates.io publishing; I imagine that @rachitnigam just manually types |
Indeed! I just manually push these crates to cargo but it is high time for us to automate this process because it's blocking us from producing new releases quickly. |
I'm enabling auto-merge to we can prepare this for the release. |
Also, should we archive the |
I've decided that this is at a point where it makes sense to merge the LSP stuff into the main Calyx mono-repo. It makes dealing with using the Calyx lib for diagnostics easier.