RubyKaigi 2026 will be at Hakodate, Japan, Apr 22th - 24th.
We would like to try to hold a face-to-face dev meeting at Hakodate. (@matz (Yukihiro Matsumoto) will also participate!)
Date: 2026/04/21 (Tue.) 15:00-17:00 (The day before RubyKaigi)
Location: RubyKaigi venue (detailed will be announced before the meeting)
If you have a ticket that you want matz and committers to discuss, please post it into this ticket in the following format:
* [Ticket ref] Ticket title (your name)
* Comment (A summary of the ticket, why you put this ticket here, what point should be discussed, etc.)
Example:
* [Feature #14609] `Kernel#p` without args shows the receiver (ko1)
* I feel this feature is very useful and some people say :+1: so let discuss this feature.
It is recommended to add a comment by 2025/04/20. I'll ask Matz which should be discussed on this meeting and reorder them.
Your comment is mandatory. We cannot read all discussion of the ticket in a limited time. We appreciate it if you could write a short summary and update from a previous discussion.
[Feature #21962] Add deep_freeze for recursive freezing (eregon)
A revised proposal that aims to address the previous discussion. Got 2 ๐.
It follows the behavior of Ractor.make_shareable, and is also consistent with IceNine.deep_freeze, so the semantics are already well understood and have existing usage.
Is Kernel#deep_freeze OK? It seems the obvious fit, given Kernel#freeze.
Semantics are are OK?
I can implement it.
[Feature #21963] A solution to completely avoid allocated-but-uninitialized objects (eregon)
How about that solution? Class#safe_initialization/rb_class_safe_initialization() + rb_initializing_alloc_func_t()?
[Feature #21795] Methods for retrieving ASTs (eregon)
Would love to make progress on this.
How about the idea to use start line/column + end line/column (or equivalently, start & end offsets)?
It would avoid issues with using different Prism versions, be simpler and more portable.