
PL Implementation/Compilers person. @UniKent PhD graduate
Joined October 2021
- Tweets39
- Following70
- Followers93
- Likes224
Ah yes I should really tweet these things myself. Yes we wrote a paper, and it is nice and great
What's this? An abstract syntax tree? A bytecode? What does that even mean anymore?
Next Wednesday, @OctaveLarose is going to explore those questions in his ICOOOLPS presentation.
Our draft paper is online already: 2025.ecoop.org/details/ICOOO…
#interpreter #design #tradeoffs
5
107
Wrote a big old thing about using @MMTkGC in our Rust-based interpreters. That was fun to make and write! octavelarose.github.io/2025/…
Had been a little while since my last post about our Rust interpreters, but I'm back to show the world that I'm relying on the unsafe keyword more now. I'm not quite sure how evil I am, let me know octavelarose.github.io/2024/…
Wrote a thing about implementing inline caching in our Rust-based AST interpreter. If anyone knows how to make Rust play more nicely with self-modifying tree structures, do let me know octavelarose.github.io/2024/…
I'm pushing the performance of our Rust-based SOM interpreters, and I wrote a quick blog post about an optimization I recently implemented. Gonna try to make this more of a regular thing for extra motivation (and hopefully valuable feedback) octavelarose.github.io/2024/…
Octave Larose retweeted
.@OctaveLarose is now presenting our OOPSLA paper:
AST vs. Bytecode: Interpreters in the Age of Meta-Compilation
2023.splashcon.org/details/s…
Research people: what would you consider your ideal balance between broadening your horizons by reading into various interesting topics you're less familiar with, and zeroing in on your main topic of interest?
1
Octave Larose retweeted
Less is More. @OctaveLarose talking about optimizing Truffle interpreters.





