Poisoning Rubinius: The _why and how.
summary
Poison implements Potion on Rubinius, compiling Potion syntax down to Rubinius bytecode and exercising the VM’s JIT, LLVM backend and GC. It parses Potion with a PEG-based parser, compiles closures, lists/tables, the query operator and class/instance paths into Rubinius instructions, and runs examples that print and return values, proving the approach works. The demo shows tradeoffs: full Ruby interop versus a message-boundary actor style, and how a small PEG parser + Rubinius code generator boots a language fast — a concrete implementation of Potion on Rubinius.
AI-written summary · about
chapters (6)
- 0:00Start
- 0:32Poison Rubinius
- 3:27_why struggled with programming
- 25:36Abstract Syntax Tree script
- 37:26integrate inter-operate
- 40:16ZOMG THANK YOU EVERYONE!!! (and @tenderlove)
