Misc #21916: DevMeeting before RubyKaigi 2026

• Status: Open
• Assignee: -

[ko1 (Koichi Sasada)]

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)

How to participate

Open to any RubyKaigi attendees who have a commit bit or who have a topic they particularly want to discuss.
Please sign up on the doorkeeper page:
https://rubyassociation.doorkeeper.jp/events/195298

The meeting will be held in a hackathon event.
Please enjoy Ruby hacking with friends if you want before the meeting.

Note: Do not forget to register RubyKaigi ticket too (see "[ruby-core:124591] Invitation to RubyKaigi 2026" from Akira).

Program

• 11:00am door open and start the Hackathon event
• 3:00pm opening and self introduction
• 3:30pm discuss topics
• 5:00pm closing and free time (closing time is depends on topics)
• 6:00pm door close

Call for agenda items

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.
• The format is strict. We'll use this script to automatically create an markdown-style agenda. We may ignore a comment that does not follow the format.
• 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.

[mame (Yusuke Endoh)]

• Related to Misc #14770: [META] DevelopersMeeting added

[byroot (Jean Boussier)]

• [Feature #21768] Remove some deprecated C APIs (nobu)
  • We have a lot of functions that have been deprecated for a very long time, could we cull some?
  • Nobu had a proposed patch: https://github.com/ruby/ruby/pull/15447
  • Ideally we'd do this before the first preview so that we can selectively re-introduce some of them if happens that they are used in the wild.

[Eregon (Benoit Daloze)]

• [Feature #21962] Add deep_freeze for recursive freezing (eregon)
  • A revised proposal that aims to address the previous discussion.
  • 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_copy_alloc_func_t()?
• [Misc #21968] The pathname gem needs a new release (eregon)
  • Would it be possible to make a new pathname release?
• [Misc #21948] benchmark gem maintainer (eregon)
  • How to get access on GitHub?
• [Misc #21922] Permissions for committers for ex-default/bundled/unbundled gems repositories (eregon)
  • Let's discuss.

[jeremyevans0 (Jeremy Evans)]

• [Feature #21871] Add Module#undef_const (jeremyevans0)
  • This was discussed at the February dev meeting, but the Redmine ticket didn't do a good job of explaining why I want this.
  • I would like to pitch for this in person and be available to answer questions about it.
  • I'll share a couple places where I would like to use this feature, taken from the main application I work on.

[kddnewton (Kevin Newton)]

• [Bug #20409] END { break }
  • Can we please statically mark this as a syntax error? It always results in a runtime error.