gramatika | lox | |
---|---|---|
3 | 1 | |
4 | 0 | |
- | - | |
0.0 | 0.0 | |
over 2 years ago | over 2 years ago | |
Rust | Rust | |
GNU General Public License v3.0 or later | GNU General Public License v3.0 or later |
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.
gramatika
-
Question about lexer and parser generators in Rust
I wrote a lexer generator. It's pretty limited and poorly architected tbh, but feel free to have a look: https://github.com/dannymcgee/gramatika
-
Official /r/rust "Who's Hiring" thread for job-seekers and job-offerers [Rust 1.57]
I'm a huge nerd for programming languages and rendering, and to that end I've been putting together a general-purpose parsing library inspired by syn and using that to power a language server for WGSL.
-
Question for experienced Rustaceans
I'm probably in the minority on this one, but I really hate writing verbose, repetitive code, so I freaking love macros. I will frequently use a one-off macro just to make something like a dispatcher function easier to read by cutting down on all the pomp and circumstance. I'm also working on a small crate that makes heavy use of proc macros, which I've already gotten a ton of mileage out of since it allows me to spin up a serviceable lexer with just a few lines of code. A lot of people really dislike macros because the source is hard to read and they're onerous to debug. They're not wrong on either of those points.
lox
-
Question for experienced Rustaceans
Using a single file per module does seem to be the most popular way to organize things in the ecosystem for whatever reason, but I personally do like to keep my files pretty short, so yeah, I usually split up non-trivial modules into a folder with submodules. You can take a look at this project for kind of an extreme example.
What are some alternatives?
openvscode-server - Run upstream VS Code on a remote machine with access through a modern web browser from any device, anywhere.
ClippyCloud - Easy way to upload and share files quickly.
qdrant - Qdrant - High-performance, massive-scale Vector Database for the next generation of AI. Also available in the cloud https://cloud.qdrant.io/
parsertl14 - C++14 version of parsertl
gram_grep - Search text using a grammar, lexer, or straight regex. Chain searches for greater refinement.
lexertl14 - C++14 version of lexertl
regex - An implementation of regular expressions for Rust. This implementation uses finite automata and guarantees linear time matching on all inputs.
lalrpop - LR(1) parser generator for Rust
django-debug-toolbar - A configurable set of panels that display various debug information about the current request/response.
gitpod - The developer platform for on-demand cloud development environments to create software faster and more securely.
chumsky - Write expressive, high-performance parsers with ease.