Contributing to the Ruby Parser

In RubyKaigi 2024 Lightning Talks Slide

Transcript

1. Contributing to the Ruby Parser S.H.
2. About Me • S.H. • Software engineer at ESM, Inc. • Hamada.rb Organizer • I’m hosting Ruby Hacking Challenge in Hamada.rb
4. ruby/ruby contributors
5. ruby/ruby contributors I’m here!
6. parse.y contributors
7. parse.y contributors I’m here!
8. Today Topic is… • Why I got interested in the Ruby Parser • How I started contributing to the Ruby Parser • How I started contributing to the Universal Parser
9. In RubyKaigi 2021 Takeout
10. In RubyKaigi 2021 Takeout • parse.y is difficult to maintain ◦ No one but nobu can maintain parse.y • parse.y seems hard to understand
11. Is parse.y really that hard to maintain?
12. I’m worried
13. I started to reading parse.y
14. My first impression of parse.y • The codebase is large • It’s hard to figure out what to begin reading • I have a no clue about BNF
15. What I read to study to parse.y • Ruby Under the Microscope • Ruby Hacking Guide • ruby trunk changes
16. I’ve started to understand parse.y a bit
17. Difficulties I noticed while reading • Ruby Parser and Ripper are interwind • The overall codebase is large
18. Difficulties I noticed while reading • Ruby Parser and Ripper are interwind • The overall codebase is large It’s too hard
19. Difficulties I noticed while reading • Ruby Parser and Ripper are interwind • The overall codebase is large May be able to do something here?
20. Let’s do it!
21. Action • Reusing BNF • Introducing some macros • Introducing Ruby C API
22. Reusing BNF (1)
23. Reusing BNF (1)
24. Reusing BNF (2)
25. Reusing BNF (2)
26. Reusing BNF (3)
27. Reusing BNF (3)
28. Introducing macro (1)
29. Introducing macro (2)
30. Introducing Ruby C API
31. Results • Cut down codebase • Added dependencies by introducing macros and Ruby C API
32. In RubyKaigi 2023
33. In RubyKaigi 2023 • I feel the future of the Ruby Parser in “The Future of the Ruby Parser” at spikeolaf • I realized that added macros and Ruby C API are make dependencies for Universal Parser
34. After RubyKaigi 2023
35. After RubyKaigi 2023 • I read “Started parse.y Refactoring Challenge” ◦ https://yui-knk.hatenablog.com/entry/202 3/06/18/162100 • It was written want to remove the generation of literal objects in parse.y
36. Why? • parse.y needs Ruby C API for generation of literal objects • Will obtain a simpler AST ◦ e.g. Fixnum, Bignum, and Float…
37. Let’s do it!
38. Introducing new NODE (1)
39. Introducing new NODE (2)
40. Reducing C API dependencies (1)
41. Results • Obtained a simpler AST for some literal ◦ e.g. Numeric and __ENCODING__ • Reducing Ruby C API dependencies for Universal Parser
42. KPT Keep motivation Should more disscuss Share my experience Increase Parser Contributor Keep Problem Try
43. parse.y is NOT Hell! We can hack parse.y!