lsp-server VS pest

You can look into RA's lsp_server example, allthough it is designed to show how to create a LSP server it showcases well how to use the lsp_types crate (which contains the definitions of LSP).

I believe the closest to a plug-and-play solution is using a server scaffold/stub. For example rust-analyzer uses this, or there is tower-lsp.

Consider “just write it yourself” option. Implementation in rust-analyzer takes about a hundred lines https://github.com/rust-analyzer/lsp-server/blob/master/src/msg.rs#L140

And some related parser tools: - https://github.com/kevinmehall/rust-peg - https://github.com/pest-parser/pest - https://github.com/lalrpop/lalrpop

I had recently completed the first year of my Computer Science class at school and will begin my second year soon. My schools' class forces the use of Java programming language, and I absolutely hated it. So, over the course of a little less than a month, I wrote my own programming language, in Rust (objectively best programming language), using pest, to be as similar to Rust as possible, but compiling to Java.

I second pest.rs. Using it is fairly intuitive and there's also a live playground on their website which is great for quickly developing and testing your AST (abstract syntax tree) parser for whatever language you're implementing.

This is where you'll run into trouble. People who write parsing-related Rust crates generally write things like pest that expect their syntax to be defined completely at compile time so the parser can be run through the compiler's optimizers for best performance.

Give https://pest.rs a try.

For now I have used pest to generate an AST that borrows from the given input. But if I can manage to make the parser generic over the return type it may be worth a refactoring.