gramatika
ClippyCloud
gramatika | ClippyCloud | |
---|---|---|
3 | 1 | |
4 | 60 | |
- | - | |
0.0 | 0.0 | |
over 2 years ago | over 1 year ago | |
Rust | TypeScript | |
GNU General Public License v3.0 or later | MIT License |
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.
ClippyCloud
-
Question for experienced Rustaceans
Is that extreme example of splitting? To me it works fine. From couple years I'm working with Vue, Nodejs, Typescript, Ruby on Rails and there this file setup you showed me are totally normal and gives good readability if made properly. I.e. look at this repo. It's kinda extreme to me. Not only about file splitting but also tests for any html component etc. Here are example graphlql api structure I've written for my projects in NodeJS + Fastify + Mercurius (GraphQL server). And you'll probably understand basic purpose of it and what should be found where. That's why I'd like to do same in Rust.
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.
template-benchmarks-rs - Collected benchmarks for templating crates written in Rust
qdrant - Qdrant - High-performance, massive-scale Vector Database for the next generation of AI. Also available in the cloud https://cloud.qdrant.io/
react-upload-box - A minimal Upload component for React.
parsertl14 - C++14 version of parsertl
mutagen - Breaking your Rust code for fun and profit
gram_grep - Search text using a grammar, lexer, or straight regex. Chain searches for greater refinement.
lox
lexertl14 - C++14 version of lexertl
django-debug-toolbar - A configurable set of panels that display various debug information about the current request/response.
regex - An implementation of regular expressions for Rust. This implementation uses finite automata and guarantees linear time matching on all inputs.
mini-vue - Implementing a minimal vue3 model for learning Vue3 in depth.