Actions
Misc #22221
openDevMeeting-2026-08-06
Misc #22221:
DevMeeting-2026-08-06
Status:
Open
Assignee:
-
Description
The next dev meeting¶
Date: 2026/08/06 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/08/03. 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.
Updated by mame (Yusuke Endoh) 2 days ago
- Related to Misc #14770: [META] DevelopersMeeting added
Updated by shugo (Shugo Maeda) 2 days ago
- [Feature #22213] Allow no-argument and chained calls of Proc#refined (shugo)
- A no-argument call returns the receiver itself, and a chained call returns a Proc with additional refinements:
prc.refined(*ms).refined(*ns)is equivalent toprc.refined(*ms, *ns) - The copy of the block is deferred until the first call, so a Proc that is never called is never copied, and a chained call is memoized like a single call with all the modules
- I'd like matz to approve this behavior
- A no-argument call returns the receiver itself, and a chained call returns a Proc with additional refinements:
- [Feature #22205] Deprecate ruby2_keywords (shugo)
- I'd like to deprecate and eventually remove ruby2_keywords; feedback on the ticket is positive, and the proposed schedule is in the description
- Should Hash.ruby2_keywords_hash? and Hash.ruby2_keywords_hash be deprecated one phase later than the marking methods (they are needed as long as flagged hashes exist), or on the same schedule?
- [Feature #9779] Add Module#descendants (shugo)
- Module#descendants returns the classes and modules that inherit or include the receiver
- Is it OK to add it to Module, not only Class?
- Is it OK that the return value does not include self?
- [Feature #22132] Scala-like for comprehensions (shugo)
- At the previous dev meeting, matz said he was interested and wanted to take time to consider it
- Does matz have any opinions or questions at this point?
Updated by Eregon (Benoit Daloze) 2 days ago
- [Feature #22212] Add Thread::Backtrace::Location#source_range (eregon)
- Proposes a portable API returning a
Ruby::SourceRangefor an exception'sbacktrace_locationsor forcaller_locations. - This gives tools stable start/end line/column coordinates without version-specific
node_idvalues (examples ofnode_idinstability). - Examples which could use this API instead of currently the CRuby-specific
RubyVM::AST.node_id_for_backtrace_location, and therefore work reliably on TruffleRuby/JRuby:
Prism.find(Thread::Backtrace::Location),Railsexception printing,error_highlight,power_assert. - It does not require the Prism gem or create
Prism::Nodeobjects, separating source-code location from parsing that code into an AST. - The implementation reparses on demand to avoid persistent memory overhead, uses source-hash validation based on @mame (Yusuke Endoh) 's work, and supports
RubyVM.keep_script_lines = trueto avoid re-reading files from disk. - Extensive specs ensure Prism and parse.y return identical user-facing coordinates, including for blocks.
- I am looking for matz's approval for the new method.
- Proposes a portable API returning a
Updated by Eregon (Benoit Daloze) 2 days ago
· Edited
- [Bug #22197] Backtraces show methods which do not exist (eregon)
- As the title says, backtraces sometimes list methods which do not exist, because of mixing definition name with run-time owner (
Method#owner). - Since we print file, line and method name from the original definition (
def), I think we should show the original module too. - Let's fix it? PR: https://github.com/ruby/ruby/pull/17963
- As the title says, backtraces sometimes list methods which do not exist, because of mixing definition name with run-time owner (
Updated by jaruga (Jun Aruga) 2 days ago
· Edited
- [Feature #22068] Adding post-quantum cryptography (PQC) support across Ruby standard libraries (jaruga)
- I explain the feature with my motivations, and answer questions from other developers.
- I want to share how to proceed for possible target libraries to modify: ruby/rubygems, bundler, ruby/net-http, ruby/open-uri, ruby/spec, ruby/drb, ruby/rbs.
Actions