Misc #21689: DevMeeting-2025-12-11

• Status: Closed
• Assignee: -

[mame (Yusuke Endoh)]

The next dev meeting

Date: 2025/12/11 13:00-17:00 (JST)
Log: https://github.com/ruby/dev-meeting-log/blob/master/2025/DevMeeting-2025-12-11.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/12/08. 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)]

• [Bug #21375] Set[] does not call #initialize (eregon)
  • This broke concurrent-ruby and there is no good fix.
  • I believe Set[] should call #initialize, it's simple and avoids a major breaking change. The performance impact seems insignificant.
  • The PR from Jeremy LGTM: https://github.com/ruby/ruby/pull/15228
  • UPDATE: merged and fixed, all good :)

[chucke (Tiago Cardoso)]

• [Feature #21619] logger context API
  • Blog post detailing motivation here
    • logger doesn't have a context API to enrich payload for structured logging
    • other languages have some of the kind (the post details examples from java, go, python)
  • PR with proposal here
    • some public API feedback to address.
    • sonots (gem maintainer) didn't reply since I opened the proposal.

logger = Logger.new(STDOUT)
logger.with_context("user_id" => 1) do
  logger.info("foo")
    #=> I, [2025-11-28T17:57:50.947152 #3705893] [user_id=1] INFO -- : foo
    # if using a hypothetical json formatter
    #=> { "message" => "foo", "user_id" => 1, ....
  end
logger.info("foo", context: { "user_id" => 1 }) #=> same thing, but single call only

[ioquatix (Samuel Williams)]

• [Feature #21704] Expose rb_process_status_new to C extensions.
  • Required for improved io_uring process_wait hook (it returns full status).
  • https://man7.org/linux/man-pages/man3/io_uring_prep_waitid.3.html
  • Is it acceptable? https://github.com/ruby/ruby/pull/15213

[knu (Akinori MUSHA)]

• [Feature #21701] Enumerator.produce accepts an optional size keyword argument
  • Enumerator#to_set now rejects infinite sequences, and the current situation of Enumerator::Producer that its size is fixed to infinity creates an inconsistency that prevents finite produce enumerators from being converted to sets.

[shugo (Shugo Maeda)]

• [Feature #21552] allow String.strip and similar to take a parameter similar to String.delete
  • pull request: https://github.com/ruby/ruby/pull/15400
  • Is it acceptable to take character selectors like String#delete?
    • Python's str.strip seems not to support ranges etc.

[mame (Yusuke Endoh)]

• [Bug #21049] Reconsider handling of the numbered parameters and "it" parameter in Binding#local_variables (mame)
  • An API like Binding#numbered_parameter_get was actually requested. I'd like to discuss how to proceed.

[pabloh (Pablo Herrero)]

• [Feature #19979] Reconsider adding &nil to method declarations, to signal it won't accept a block
  • Adding this feature should be possible now that the syntax moratorium is over

[Eregon (Benoit Daloze)]

• [Feature #8948] Frozen regex (eregon)
  • This is to make all Regexps frozen and not just literals.
  • I made a PR, it passes CI: https://github.com/ruby/ruby/pull/14547
  • Is it OK to merge it for Ruby 4.0?

[Eregon (Benoit Daloze)]

• [Feature #21766] Pathname + FileUtils making sweet music together (eregon)
  • These methods are useful and in fact are expected by some to already exist on Pathname.
  • How should we add them given they depend on FileUtils?

[k0kubun (Takashi Kokubun)]

• [Misc #21769] Use "vX.Y.Z" instead of "vX_Y_Z" as tag names on ruby.git (k0kubun)
  • I want Ruby 4.0.0 to use v4.0.0 as its git tag name instead of v4_0_0. If we release rc1, can we call it v4.0.0-rc1 too?
  • Do we also want to drop v and make it 4.0.0 like @jeremyevans0 (Jeremy Evans) proposed?
• [Misc #21770] Stop bumping RUBY_PATCHLEVEL in release versions (k0kubun)
  • I want to update tool/merger.rb to skip updating RUBY_PATCHLEVEL for Ruby 4.0.0+. Is that okay?

[mame (Yusuke Endoh)]

@chucke (Tiago Cardoso) Please follow the instruction next time:

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.

This time I modified your comment.

[mame (Yusuke Endoh)]

• Status changed from Open to Closed

[mame (Yusuke Endoh)]

• Description updated (diff)