Misc #21877: DevMeeting-2026-03-17

• Status: Open
• Assignee: -

[mame (Yusuke Endoh)]

The next dev meeting

Date: 2026/03/17 13:00-17:00 (JST)
Log: TBD

• Dev meeting IS NOT a decision-making place. All decisions should be done at the bug tracker.
• Dev meeting is a place we can ask Matz, nobu, nurse and other developers directly.
• Matz is a very busy person. Take this opportunity to ask him. If you can not attend, other attendees can ask instead of you (if attendees can understand your issue).
• We will write a record of the discussion in the file or to each ticket in English.
• All activities are best-effort (keep in mind that most of us are volunteer developers).
• The date, time and place of the meeting are scheduled according to when/where we can reserve Matz's time.
• DO NOT discuss then on this ticket, please.

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 2026/03/14. We hold a preparatory meeting to create an agenda a few days before the dev-meeting.
• 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

[synacker (Mikhail Milovidov)]

• [Feature #21869] Add receive_all Method to Ractor API for Message Batching
  • This feature is essential for high‑load services because message batching is a highly efficient technique for reducing the number of expensive I/O requests and minimizing context switches between Ractors and business logic
  • The feature opens the way to vectorized message handlers, enabling batch processing of messages in a single handler invocation.
  • The proposal has received positive feedback from the community on GitHub, Reddit, and Discord
  • I have created a PR on GitHub: https://github.com/ruby/ruby/pull/16105

[Earlopain (Earlopain _)]

• [Feature #21875] Handling of trailing commas in lambda parameters (earlopain)
  • Followup to Feature #19107 (Allow trailing comma in method signature)
  • During implementation I noticed that lambdas in the style of ->() never came up
  • In addition to the ticket description, @Eregon (Benoit Daloze) created a good comparison in https://bugs.ruby-lang.org/issues/21875#note-2
  • There are a few ways that a trailing comma could be handled but I think it would be best to just reject it. It's confusing and I don't think there is a use-case (if one comes up, we can reconsider).