Evolution Of Keyword Parameters
summary
History and concrete changes to keyword parameters in Ruby from the hash-based hack to a real calling convention are explained, with an MRI C implementation and compiler+VM changes that add a keyword table and new dispatch paths. A prototype runs on Ruby 2.2/2.3-era code, replaces heavy splat/merge work, and passes unit tests. Microbenchmarks and a Rails-style workload show reduced call overhead — roughly 20–40% faster call overhead on keyword-heavy paths — and the new approach interoperates with default values and keyword splatting.
AI-written summary · about
chapters (5)
- 0:00Introduction and welcome
- 6:36Ruby keyword parameters overview
- 13:23History and evolution
- 20:00Practical use cases
- 27:22Q&A and summary
related talks
30mRuby keyword args and the options hash, from the parser to the virtual machine
17mKeyword Args — the killer Ruby feature you aren't using
53mRuby 2 in Ruby on Rails
42mRuby 2 Methodology
29mKeynote: Reinventing Wheels of the Future
49mHow are Method Calls Formed?
39mState of the Ruby
38mCool, But... Why?