Misc #21399: DevMeeting-2025-07-10

• Status: Open
• Assignee: -

[mame (Yusuke Endoh)]

The next dev meeting

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

[Eregon (Benoit Daloze)]

• [Feature #17473] Make Pathname to embedded class of Ruby (eregon)
  • Related to that issue and discussed there, I made a PR to define most of Pathname in Ruby: https://github.com/ruby/pathname/pull/53
  • It's faster, easier to read and maintain and enables sharing most of the Pathname implementation between Ruby implementations.
  • Could @akr (Akira Tanaka) review it? I wrote him on Slack but got no reply, maybe a committer knows better how to contact him?
  • If @akr (Akira Tanaka) is not available, please let me know and I will try to find another reviewer.

[ioquatix (Samuel Williams)]

• [Bug #19473] can't be called from trap context (ThreadError) is too limiting
  • Can we change the behaviour? https://github.com/ruby/ruby/pull/13545
  • Or should we consider alternatives, e.g. Mutex#safe_in_trap_context?
• [Bug #21360] Inconsistent Support for Exception#cause in Fiber#raise and Thread#raise
  • Can we fix the consistency issues?

[tenderlovemaking (Aaron Patterson)]

• [Feature #21140] Add a method for getting addresses of certain functions for 3rd party JITs
  • RJIT has been extracted to a gem, but it can't work without getting the address of certain functions
  • Not all JIT related functions are exported, so dlsym can't get the address
  • Proposed API is like this: RubyVM::Internals.address_of(:rb_vm_ci_argc), where rb_vm_ci_argc is the function we want the address for
    • If the function exists, it returns the address
    • If not, it returns nil
  • This API should not make guarantees about stability or portability
  • I have no strong feelings about the method or constant name, but RubyVM::Internals tries to communicate this is an internal and unstable API

[hsbt (Hiroshi SHIBATA)]

• [Feature #21442] Make tsort to bundled gems
  • Any objection for this?

[Eregon (Benoit Daloze)]

• [Feature #21039] Ractor.make_shareable breaks block semantics (seeing updated captured variables) of existing blocks
  • How about Ractor.make_shareable { ... } which only allows literal block?
  • That avoids the well known problem of a block body being reinterpreted in different ways (like the same block as proc & lambda, or in this issue like a regular block and a block-with-snapshot-of-the-environment).
  • See https://bugs.ruby-lang.org/issues/21039#note-11 for details