rustykey
tower-lsp
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
rustykey
-
What's everyone working on this week (22/2023)?
Im continuing rustykey, nearly ready for v1.0 and been streaming im working on it along the way https://m.twitch.tv/sean_borg
- What's everyone working on this week (20/2023)?
tower-lsp
-
What's everyone working on this week (22/2023)?
I am using nom / nom_locate to build the parser side because I've done a handful of other projects with it, and I plan to use tower-lsp to hook up the language server side.
-
State of the Ruby language server (LSP) ecosystem / looking for suggestions
I realize this might not be for everyone, but I'm writing it in Rust using Lib-ruby-parser and tower-lsp: two existing libraries that handle a bunch of the heavy lifting for me. I'm more productive in Rust than with Ruby at this point, despite doing Ruby full time for 15 years, plus I really really don't want to have to deal with a slow LSP--that was the whome impetus for this project. I started in the spring, made a bunch of headway, then backtracked to redo the internals to make it easier to handle monkeypatching, overriding/redefining of methods, etc. across your project.
-
Language Server Protocol
https://github.com/ebkalderon/tower-lsp is a generalized LSP implementation in a lower-level language (Rust) so you may get a better idea by reading through that repo. It seems that the server opens a TCP socket that the client later connects to, but I'm not really sure.
-
tower_lsp client/server Document Sync
I was taking a look at the tower_lsp example here (https://github.com/ebkalderon/tower-lsp/blob/master/examples/stdio.rs) and had a question about how the document sync works between the client and the server.
-
how to make a lsp in rust ?
Mine all use [tower-lsp](https://github.com/ebkalderon/tower-lsp/) for the LSP protocol stuff, and then either [Tree-sitter](https://github.com/tree-sitter/tree-sitter) or [Nom](https://github.com/Geal/nom). If I do another I'll probably try [Chumsky](https://github.com/zesterer/chumsky) which combines some of the advantages of both.
- tower-lsp 0.16.0 — Lightweight framework for building LSP servers
What are some alternatives?
arp_standin - Proof of concept for responding to ARP requests on behalf of another machine. (Deprecated by https://github.com/danielpgross/friendly_neighbor)
tower - async fn(Request) -> Result<Response, Error>
RustNet - A rust API (and solid.js frontend) for a neural net
kakoune-lsp - Kakoune Language Server Protocol Client
krust-manifesto - Abstractions to write concise Kubernetes manifests using Rust
rust-analyzer - A Rust compiler front-end for IDEs
vault-server - Rust REST API server and white-label SolidJS UIs for semantic search and RAG/no-hallucination LLM-chat [Moved to: https://github.com/arguflow/arguflow]
tree-sitter - An incremental parsing system for programming tools
intelli-shell - Like IntelliSense, but for shells
react-relay - Relay is a JavaScript framework for building data-driven React applications.
LMDB-editor - A small LMDB editor made in Rust with egui
chumsky - Write expressive, high-performance parsers with ease.