swifties
rhizome
Our great sponsors
| swifties | rhizome | |
|---|---|---|
| 5 | 8 | |
| 11 | 814 | |
| - | - | |
| 0.0 | 1.8 | |
| over 2 years ago | almost 3 years ago | |
| Swift | Ruby | |
| - | 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.
swifties
-
Let's write a compiler, part 5: A code generator
Depends on the complexity of your queries, but if you have a narrow subset that you're interested in, implementing a recursive descent parser for just those parts of the syntax that fits your problem like a glove could be a better solution.
https://github.com/codr7/swifties
- Show HN: Swifties – a custom language construction kit in Swift
-
Let's write a compiler, part 3: A parser
What few seem to realize is that it's perfectly possible to abstract out some of the work and create an extensible foundation for manual parsers.
Since it's all regular code, you can use the full power of the host language to deal with the problem.
https://github.com/codr7/swifties/blob/main/Sources/Swifties...
rhizome
- How do optimizing compilers convert variables into registers
- YJIT: Building a New JIT Compiler for CRuby
-
Tenderjit – A JIT for Ruby Written in Ruby
There was actually an existing, similar in concept, Ruby JIT, Rhyzome: https://github.com/chrisseaton/rhizome.
It's good to see (IMO) the development of a JIT in a strict sense. I'm personally skeptical about the current approach (invoking a compiler separately).
On the other hand, it's important to know that JITs may take a long development time to be performant, and that they also complicate the performance profile of a virtual machine.
-
Let's write a compiler, part 5: A code generator
Lots of compiler tutorials are like this - there's very little out there to explain how compilers really work.
This is my effort - trying to show genuine data structures and processes.
https://github.com/chrisseaton/rhizome
- Thoughts about Intermediate representations
- A JIT for Ruby, implemented in pure Ruby (/r/ruby)
- Rhizome – a JIT for Ruby, implemented in pure Ruby
What are some alternatives?
sqlite-parser - JavaScript implentation of SQLite 3 query parser
yjit - Optimizing JIT compiler built inside CRuby
langjam
pl0c - Self-hosting PL/0 to C compiler to teach basic compiler construction from a practical, hands-on perspective.
grammars-v4 - Grammars written for ANTLR v4; expectation that the grammars are free of actions.
zetasql - ZetaSQL - Analyzer Framework for SQL
vitess-sqlparser - simply SQL Parser for Go ( powered by vitess and TiDB )
FLOX - An adaptation of the interpreter from the book 'Crafting Interpreters' by Robert Nystrom written in F#
mb-sound - A library of simple Ruby tools for processing sound.