Misc #22394: DevMeeting-2026-10-07

• Status: Open
• Assignee: -

[hsbt (Hiroshi SHIBATA)]

The next dev meeting

Date: 2026/10/07 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/10/04. 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.

[hsbt (Hiroshi SHIBATA)]

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

[byroot (Jean Boussier)]

• [Feature #22395] RubyVM::InstructionSequence.load_from_binary to optionally accept file and path arguments like compile (byroot)
  • ISeq caching has a long live problem that ISeqs contain the source file path and realpath, making Iseq "non-portable". See [Feature #17593].
  • To solve this, I think we need to be able to provide the new path and realpath when loading an ISeq from binary. Which means extending some APIs.
  • Proposed: load_from_binary(binary [, file[, path]]), similar to the existing compile(source[, file[, path[, line[, options]]]]).
  • Also C API: VALUE rb_iseq_load_from_binary(const char *ptr, size_t len, VALUE file, VALUE path). The later argument can be set to nil.