Practical TypeProf: Lessons from Analyzing Optcarrot
summary
TypeProf applied to Optcarrot (a 6,000-line NES emulator) finds 669 false-positive errors initially and is driven to zero by a mix of targeted RBS at bottlenecks and small code fixes: adding three RBS hooks around memory access and one-line nil→0 initialization drops errors dramatically. Total edits are 122 lines (55 changes, 67 additions). Comparison: Steep ~1,429 lines, Sorbet ~1,248 lines. TypeProf on Optcarrot 669 → 0 errors 122-line patch AI finds key points but misses one bug
AI-written summary · about
chapters (7)
- 0:00Introduction and announcements
- 2:17What is TypeProf
- 9:38Applying TypeProf to Optcarrot
- 18:23Reducing false positives
- 22:50Comparison with other type checkers
- 25:04TypeProf in the AI era
- 30:14Future work and conclusion
related talks
36mA Static Type Analyzer of Untyped Ruby Code for Ruby 3
56mThe Rational Programmer, An Investigative Method for Programming Language Prag...
28mA Plan towards Ruby 3 Types
42mTypes As Premature Optimization
42mSurprise yourself with Property Based Testing
18mPreview: Verification (Correctness & Debugging)
31mStatic Type Checking in Rails with Sorbet
32mGradual Typing in Ruby - A Three Year...