No Types Needed, Just Callable Method Check
summary
Claims that the only essential static check in many Ruby workflows is that a called method actually exists and builds a CI-first tool to do just that. The gem method_array uses Rust for speed, the Ruby prism parser and a bumper allocator, plus a graph-based flow like TypeProf to report no method error with exact file, line and column. It runs single-file today, catches missing methods quickly in CI, and plans multi-file, gem-stdlib resolution next.
AI-written summary · about
chapters (12)
- 0:00Introduction and speaker intro
- 1:49One-line summary of the talk
- 2:12Benefits of types in Ruby
- 6:49How AI changed the game for Ruby
- 9:20Do we need types in the AI era?
- 12:30Guardrails for AI-generated code
- 14:19Introducing method_array gem
- 15:24How method_array works
- 21:05Why Rust for method_array
- 22:53Comparison with Steep and TypeProf
- 24:43Future roadmap for method_array
- 25:45Final thoughts and call to action
