Static Typo Checker in Ruby
summary
A static typo checker is implemented as a did_you_mean static mode that parses bytecode via RubyVM InstructionSequence to list undefined method calls without executing app logic, and it exposes findings as JSON to editors via a VS Code plugin for inline annotations. It works well on small, dependency-light projects and JRuby, but it still spawns a Ruby process, yields many false positives with ActiveRecord metaprogramming and method_missing, and needs Rails-aware filters and caching to scale.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 2:10What is a champion
- 11:17Problems with did you mean
- 14:29Static analysis demo
- 17:44How static checker works
- 23:05Editor integration
- 29:14Limitations and challenges
- 36:03Conclusion and future
- 37:55Q&A
related talks
31mStatic Type Checking in Rails with Sorbet
24mType Checking with Sorbet
26mSemi Automatic Code Review
54mKeynote – Aaron Patterson
29mA Rails Developer’s Guide To The Ruby VM
30mLeveling Up Developer Tooling For The Modern Rails & Hotwire Era
36mWhy Ruby Isn't Slow
57mFuture of Developer Acceleration with Rails