Actions
Misc #21606
closedDevMeeting-2025-10-23
Misc #21606:
DevMeeting-2025-10-23
Status:
Closed
Assignee:
-
Description
The next dev meeting¶
Date: 2025/10/23 13:00-17:00 (JST)
Log: https://github.com/ruby/dev-meeting-log/blob/master/2025/DevMeeting-2025-10-23.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/10/20. 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 months ago
- Related to Misc #14770: [META] DevelopersMeeting added
Updated by kddnewton (Kevin Newton) 2 months ago
- [Feature #21572] Make illegal variable in alternation pattern a syntax error (kddnewton)
- Can we make this into a parse-time syntax error as opposed to a compiler error?
Updated by k0kubun (Takashi Kokubun) 2 months ago
- [Misc #21609] Propose Stan Lo (@st0012 (Stan Lo)) as a core committer (k0kubun)
- To speed up the ZJIT development, can we let him merge his PRs by himself?
Updated by tenderlovemaking (Aaron Patterson) about 2 months ago
- [Feature #20163] Add Integer#popcount
- Add a method for counting "on" bits in an integer
- Raises an exception for negative numbers
- Method would be helpful for bitsets, bitboards, and other data structures
Updated by Eregon (Benoit Daloze) about 1 month ago
- [Bug #21640] Core Pathname is missing 3 methods / is partially-defined (eregon)
- This seems a bad user experience: partially-defined class missing some methods,
require "pathname"doesn't load the gem as expected (even with Bundler), etc - I think it would be better to keep Pathname as a default gem and not core, it avoids all 6 problems.
- If we absolutely must have Pathname in core, how to fix these 6 problems then?
- This seems a bad user experience: partially-defined class missing some methods,
Updated by matheusrich (Matheus Richard) about 1 month ago
- [Feature #21615] Introduce
Array#values- Seems reasonable to have an API to simplify traversal of hash/array values
- There is some precedence, since both Hashes/Arrays have #values_at.
- If approved, should it be added to Set too?
Updated by jhawthorn (John Hawthorn) about 1 month ago
- [Misc #21646] Propose Luke Gruber as a Ruby committer (jhawthorn)
- Luke has been fixing bugs in Ractors and elsewhere. Would be helpful if he could merge his own PRs.
Updated by kddnewton (Kevin Newton) about 1 month ago
- [Misc #21630] Suggest @Earlopain for core contributor
- They have been very helpful for Prism maintenance, and also other areas of Ruby. It would be helpful for them to merge their own PRs.
Updated by kddnewton (Kevin Newton) about 1 month ago
- [Feature #21573] Simpler syntax errors
- Developers want nice syntax errors in the command line, that is implemented today.
- Language-agnostic tools that parse stdout want simple-to-parse errors and warnings.
- Can we add a mode/switch/environment variable/some other mechanism to trigger this?
Updated by mame (Yusuke Endoh) about 1 month ago
- Description updated (diff)
- Status changed from Open to Closed
Actions