Misc #21134: DevMeeting-2025-03-13

• Status: Closed
• Assignee: -

[mame (Yusuke Endoh)]

The next dev meeting

Date: 2025/03/13 13:00-17:00 (JST)
Log: https://github.com/ruby/dev-meeting-log/blob/master/2025/DevMeeting-2025-03-13.md

• 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 2025/03/10. 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

[jeremyevans0 (Jeremy Evans)]

• [Bug #21089] Missing methods on enumerators created from Enumerator::product and Enumerator::Chain (jeremyevans0)
  • Is this behavior expected?
  • It seems odd that it doesn't work by default, but it does work if you call to_enum.
  • Maybe we should have to_enum called implicitly so that it works, unless there are performance or other reasons not to?
• [Bug #21026] def __FILE__.a; end should be a syntax error (jeremyevans0)
  • I'm not sure it is worth making this a syntax error.
  • Do we want to make this change?
• [Bug #21016] What should massign with shareable_constant_value: experimental_everything freeze? (jeremyevans0)
  • What is the desired behavior in this case?
• [Bug #20968] Array#fetch_values unexpected method name in stack trace (jeremyevans0)
  • I think this is expected behavior and not a bug.
  • If we consider this a bug, how do we plan to address it as we move methods from C to Ruby?

[ioquatix (Samuel Williams)]

• [Bug #21166] Fiber Scheduler is unable to be interrupted by IO#close.
  • Introduce new public interfaces:
    • VALUE rb_fiber_scheduler_fiber_interrupt(VALUE scheduler, VALUE fiber, VALUE exception) for interrupting a specific fiber on the fiber scheduler.

[mame (Yusuke Endoh)]

• Description updated (diff)
• Status changed from Open to Closed

[mame (Yusuke Endoh)]

The next dev meeting will be held at RubyKaigi 2025, Matsuyama, face to face. Please write to #21100 for the agenda.