From: "Eregon (Benoit Daloze) via ruby-core" Date: 2026-11-09T16:35:44+00:00 Subject: [ruby-core:127386] [Ruby Misc#22417] DevMeeting-2026-11-12 Issue #22417 has been updated by Eregon (Benoit Daloze). * [Feature #22523] define_method should make its body shareable when possible, using Ractor.shareable_proc semantics (eregon) * As proposed in #21557, and like #22444 did for `Ractor.new`: `define_method`/`define_singleton_method` make the body shareable as if by `Ractor.shareable_proc(self: nil)` when possible, and otherwise define the method exactly as before (never raises). * Methods whose body only reads outer variables which are never reassigned and hold shareable values (the common case) become callable from any Ractor, without workarounds like the one in `ostruct`. * The captured variables then become constants for the method, which allows folding them at definition time (in JITs or in the bytecode), making such methods as fast as the equivalent `def`. * This relies on 3 bug fixes for `Ractor.shareable_proc`: #22521, #22522, #22524. * OK to merge it? PR: https://github.com/ruby/ruby/pull/19801 ---------------------------------------- Misc #22417: DevMeeting-2026-11-12 https://bugs.ruby-lang.org/issues/22417#change-119832 * Author: mame (Yusuke Endoh) * Status: Open ---------------------------------------- # The next dev meeting **Date: 2026/11/12 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/11/09. 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](https://gist.github.com/mame/b0390509ce1491b43610b9ebb665eb86). 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. -- https://bugs.ruby-lang.org/ ______________________________________________ ruby-core mailing list -- ruby-core@ml.ruby-lang.org To unsubscribe send an email to ruby-core-leave@ml.ruby-lang.org ruby-core info -- https://ml.ruby-lang.org/mailman3/lists/ruby-core.ml.ruby-lang.org/