crafting-interpreters-rs
Crafting Interpreters in Rust (by tdp2110)
lexgen
A fully-featured lexer generator, implemented as a proc macro (by osa1)
| crafting-interpreters-rs | lexgen | |
|---|---|---|
| 1 | 4 | |
| 231 | 60 | |
| - | - | |
| 0.0 | 5.9 | |
| over 1 year ago | 3 months ago | |
| Rust | Rust | |
| Boost Software License 1.0 | MIT License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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.
crafting-interpreters-rs
Posts with mentions or reviews of crafting-interpreters-rs.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-05-10.
lexgen
Posts with mentions or reviews of lexgen.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-05-06.
-
How are macros dealt with for incremental compilation?
Indeed this is the problem I'm having with my proc macro crates lexgen and parsegen. In the case of lexgen, the proc macro is actually quite fast for realistic inputs, but the compiler spends a lot of time checking and generated code with cargo check (which I suspect rust-analyzer also uses). In the case of parsegen the proc macro does some analyses and takes some time. In both cases I have to split my proc macro code (not the proc macros, the code that uses the proc macros) to separate crates so that they won't be recompiler/re-analyzed as I work on the code.
-
If you're not using a lexer generator for your compiler, why?
My lexer generator can handle unicode too. It's not too difficult to implement.
- A fully-featured lexer generator for Rust, implemented as a proc macro
What are some alternatives?
When comparing crafting-interpreters-rs and lexgen you can also consider the following projects:
cranelift-jit-demo - JIT compiler and runtime for a toy language, using Cranelift
logos - Create ridiculously fast Lexers
slang-v2 - Simple scripting language interpreter
parsegen - An LR parser generator, implemented as a proc macro
blip - a programming language
clojurust - A proof of concept version of Clojure in Rust.
lineiform - A meta-JIT library for Rust interpreters
hush - Hush is a unix shell based on the Lua programming language
micro-mitten - You might not need your garbage collector
RustPython - A Python Interpreter written in Rust
crafting-interpreters-rs vs cranelift-jit-demo
lexgen vs logos
crafting-interpreters-rs vs slang-v2
lexgen vs parsegen
crafting-interpreters-rs vs blip
lexgen vs clojurust
crafting-interpreters-rs vs lineiform
lexgen vs hush
crafting-interpreters-rs vs clojurust
lexgen vs micro-mitten
crafting-interpreters-rs vs RustPython