lexertl14
gramatika
| lexertl14 | gramatika | |
|---|---|---|
| 3 | 3 | |
| 48 | 4 | |
| - | - | |
| 6.2 | 0.0 | |
| 2 months ago | over 2 years ago | |
| C++ | Rust | |
| - | 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.
lexertl14
-
Show HN: Yacc/Lex editor/tester online
I'm building an online yacc/lex (LALR(1)) grammar editor/tester to help develop/debug/document grammars, the main repository is here https://github.com/mingodad/parsertl-playground and the online playground with several non trivial examples is here https://mingodad.github.io/parsertl-playground/playground/ .
Select a grammar/example from "Examples" select box and then click "Parse" to see a parser tree for the source in "Input source" editor.
It's based on https://github.com/BenHanson/gram_grep and https://github.com/BenHanson/lexertl14 .
Any feedback is welcome !
The grammars available so far (with varying state of correctness):
- Ada parser
- Question about lexer and parser generators in Rust
- Why no more Lex/Yakk/ANTLR/whatever?
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.
What are some alternatives?
parsertl14 - C++14 version of parsertl
openvscode-server - Run upstream VS Code on a remote machine with access through a modern web browser from any device, anywhere.
bpr_cpp_lexer_mirror - Compile time generated lexical analyzers.
ClippyCloud - Easy way to upload and share files quickly.
PEGTL - Parsing Expression Grammar Template Library
qdrant - Qdrant - High-performance, massive-scale Vector Database for the next generation of AI. Also available in the cloud https://cloud.qdrant.io/
lalrpop - LR(1) parser generator for Rust
chumsky - Write expressive, high-performance parsers with ease.
gram_grep - Search text using a grammar, lexer, or straight regex. Chain searches for greater refinement.
regex - An implementation of regular expressions for Rust. This implementation uses finite automata and guarantees linear time matching on all inputs.