Namespace and Its Future

#rubykaigi_followup

Transcript

1. “THE END OF NAMESPACE” Namespace and Its Future Satoshi Tagomori (@tagomoris) RubyKaigi 2025 follow up - 2025-08-30 #rubykaigi_followup
2. ా᝷ ૱ (Satoshi Tagomori) @tagomoris ͘͞ΒΠϯλʔωοτ (2024.08ʙ) Ϋϥ΢υࣄۀຊ෦ ϓϩμΫτϚωʔδϟ Maintainer/Founder: OSS: Ruby, Fluentd, MessagePack, 
 Norikra, Woothee, …
 Event: ISUCON Service: Pathtraq
3. This Talk • RubyKaigi 2025 and a Month • Namespace In the Master Branch • of “Theirs” • of tagomoris • The End of Namespace
4. What ’ s “Namespace”? • Check “Namespace, What and Why” • A new feature to create boxes to separate de fi nitions IUUQTTQFBLFSEFDLDPNUBHPNPSJTOBNFTQBDFXIBUBOEXIZ
5. “State of Namespace” • Talked about debugging IUUQTTQFBLFSEFDLDPNUBHPNPSJTTUBUFPGOBNFTQBDF
6. RubyKaigi 2025 Unexpected&Surprising Push from Matz In Matz ’ s ending keynote: “Zjit will be merged sooner…. And, I expect that the Namespace would be merged too in the next week or after the next. Is it OK?”
7. RubyKaigi 2025 Unexpected&Surprising Push from Matz In Matz ’ s ending keynote: “Zjit will be merged sooner…. And, I expect that the Namespace would be merged too in the next week or after the next. Is it OK?” “No, No〜〜〜!” 😱
8. Two Weeks Later (-1 day)
10. 10 A committer (tagomoris) merged Namespace!
11. Namespace in the Master Branch of “Theirs” • Fields - Rearchitected Object Shape (by byroot) • Instance variable management of classes/modules • Introduced just after RubyKaigi 2025, then updated w/ Namespace • Minimize memory usage around Namespace by updating memory layout (by byroot) • And others on rb_classext_t (by byroot, jhawthorn and eileencodes) • Fix SEGV on mmtk checks (by Peter Zhu) • Added Namespace#eval (by tenderlove)
12. Namespace in the Master Branch of tagomoris • Some minor bug fi xes • “Namespace management using control frame” • Updating namaspace management from 2 stacks to control frames (rb_control_frame_t) • Still WIP
14. Debug…
15. THE END OF NAMESPACE
16. The name of “Namespace” Top level “Namespace” will break something • If Ruby 3.5 will be released with the top level “Namespace”… • It breaks GitLab! 😱 • The name should… • NOT con fl ict existing classes/modules (at least, major libs/apps) • Show its feature and concept
17. TOJQ IUUQTCVHTSVCZMBOHPSHJTTVFT
18. Namespace -> Ruby::Box
19. Now we ’ re building Ruby::Box. Stay tuned! 🏗🏢👷👷🚧🏬