Popping Into CRuby
summary
Claim: CRuby’s compiler carries a popped optimization that never emits instructions for literal values proven unused, so a trailing literal like 2023 removes a previous put_string instruction and leaves only the return instructions. Evidence: compiler passes a popped flag down the AST during codegen, literals and pure literal containers get elided, while method calls, assignments or returns block popping. Work includes a new compiler front for the prism parser that aims to emit compatible YARV bytecode; integration work is ongoing toward Ruby 3.3.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:06Popped parameter in CRuby
- 3:57From Ruby code to abstract syntax trees
- 7:29Prism parser benefits
- 9:13Prism vs CRuby errors
- 12:30Parse trees to bytecode
- 14:37YARV as a stack-based virtual machine
- 17:12Popped in bytecode
- 18:56Compiler optimizations
- 21:03How popped removes unnecessary stack operations
- 22:48What can be popped
- 24:15Recursive passing of popped through the tree
- 25:19Why popped matters
- 26:00Resources
