Talks
Speakers
Events
Topics
Sign in
Home
Talks
Speakers
Events
Topics
Leaderboard
Use
Analytics
Sign in
Suggest modification to this talk
Title
Description
RubyKaigi2017 http://rubykaigi.org/2017/presentations/yuki24.html Since 2.3.0, Ruby comes with a dynamic typo checker called the did_you_mean gem, which helps find a bug caused by a typo. However, there's one argument against its design: it runs a naming check at runtime. So what makes it difficult to implement a static typo checker? What are the technical challenges to build it? Is Type really necessary? In this talk, we'll discuss techniques for how to write a static typo checker by looking at examples that find an undefined method without running Ruby code. Join us to learn about the future of Ruby's typo checker.
Date
Summarized using AI?
If this talk's summary was generated by AI, please check this box. A "Summarized using AI" badge will be displayed in the summary tab to indicate that the summary was generated using AI.
Show "Summarized using AI" badge on summary page
Summary
Markdown supported
In the video "Static Typo Checker in Ruby" presented by Yuki Nishijima at RubyKaigi 2017, the speaker discusses the challenges and methodologies for developing a static typo checker for Ruby, addressing the limitations of the dynamic typo checker known as the 'did_you_mean' gem. Key points discussed include: - **Overview of the 'did_you_mean' Gem**: Introduced in Ruby 2.3.0, this gem identifies typo-related bugs by providing correct method names at runtime, which can slow down performance due to the overhead involved in executing Ruby code during error detection. - **Challenges of Creating a Static Typo Checker**: The need to check for typos without the overhead of running Ruby scripts. The speaker emphasizes that static analysis could provide more efficient error detection at compile time, especially in larger applications. - **Technical Aspects**: The presentation explores existing problems with the 'did_you_mean' gem, including its runtime lookup method. The discussion pivots towards the potential of static analysis to minimize runtime errors by identifying mistakes before code execution. - **Demo of the Static Checker**: A demonstration shows how a static checker can identify typos in method calls without executing any code, making the analysis efficient and reducing debugging time. - **Tools for Static Analysis**: Mentioned is the use of the 'Parser' gem for Ruby syntax trees and 'RubyVM::InstructionSequence' for lower-level instruction analysis as potential resources for developing a static checker. The prototype discussed aims to highlight undefined method calls effectively, enhancing the overall robustness of Ruby code. - **Need for Continuous Improvement**: As Ruby is a dynamic language, complexities arise with method definitions and metaprogramming. Static analysis provides a pathway to reduce errors and maintain code quality. In conclusion, Nishijima emphasizes the importance of evolving Ruby's tools and methodologies to support more efficient coding practices, allowing for clearer and more accurate development environments. The session ends with an invitation for collaboration and discussion among Ruby developers to improve the language further.
Suggest modifications
Cancel
