Project

General

Profile

Actions
Copy link

Misc #21647

open

DevMeeting-2025-11-13

Misc #21647: DevMeeting-2025-11-13

Added by mame (Yusuke Endoh) 18 days ago. Updated about 12 hours ago.

Status:
Open
Assignee:
-
[ruby-core:123538]

Description

The next dev meeting

Date: 2025/11/13 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/11/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.

Related issues 1 (1 open — 0 closed)

Updated by mame (Yusuke Endoh) 18 days ago Actions
Copy link
 #1

  • Related to Misc #14770: [META] DevelopersMeeting added

Updated by Eregon (Benoit Daloze) 14 days ago Actions
Copy link
 #2

  • [Feature #20205] Enable frozen_string_literal by default (eregon)
    • Let's decide in which release the chilled string deprecation warning shows up regardless of verbosity level (R1) to make progress on this. How about 4.0?
    • Otherwise in 10 years all Ruby files will still have to begin with frozen_string_literal: true to not be a performance trap.

Updated by tenderlovemaking (Aaron Patterson) 11 days ago Actions
Copy link
 #3 [ruby-core:123625]

  • [Bug #21654] Set#new calls extra methods compared to previous versions

    • Set#new is calling "size" on its input, this is causing extra database queries in our app
    • The bug was introduced in d4020dd5faf28486123853e7f00c36139fc07793 in order to detect Set.new(0..)
    • I think we should revert d4020dd5faf28486123853e7f00c36139fc07793 and allow Set.new(0..) to hang

  • [Feature #20163] Add Integer#popcount

    • Matz asked for real-world use cases, and I provided one
    • Bit arrays can be used to represent undirected graphs, and "popcount" allows us to count edges

Updated by Earlopain (Earlopain _) 5 days ago · Edited Actions
Copy link
 #4 [ruby-core:123701]

  • [Bug #20409] Missing reporting some invalid breaks (kddnewton)
    • The main point of the issue is already resolved in both parsers
    • END { break } is not a syntax error in any parser
    • Any reason not to treat END { break } the same as BEGIN { break } which is invalid?
    • Implementation for prism here https://github.com/ruby/prism/pull/3707

Updated by alanwu (Alan Wu) 5 days ago Actions
Copy link
 #5 [ruby-core:123708]

  • [Bug #21498] Windows - Ruby Overrides C Library APIs thus breaking them (alanwu)
    • TL;DR linking with ruby.dll overrides some libc symbols on Windows
    • The ticket proposes to stop all overrides, is that acceptable?
    • If not, removing the override for specifically fclose() seems to practically fix the problem for reports cited in the ticket. How about that?
    • If we keep the fclose() override, it's hard or impossible for C99 extensions to access the standardized version of the function.

Updated by viralpraxis (Iaroslav Kurbatov) 4 days ago Actions
Copy link
 #6 [ruby-core:123720]

  • [Feature #21637] tracepoint: add support for global variables read/write events (viralpraxis)
    • There seems to be no straightforward way to trace gvar reads/writes in runtime
    • Kernel.trace_var only works when gvar name is known in advance
    • global_variables hash does not provide enough granularity
    • that would be beneficial for a runtime analysis Ruby tools I'm working on
    • it’s unclear whether "special" gvars (like $! or $LOAD_PATH) should be traced

Updated by kddnewton (Kevin Newton) about 12 hours ago Actions
Copy link
 #7 [ruby-core:123755]

  • [Feature #21678] Enumerable#rfind
    • This method would be useful for finding the last instance of something in a list.
    • There is precedence with index/rindex.
    • A lot of people are using reverse_each.find, which is not as nice.
    • Can I add this method?
Actions
Copy link

Also available in: PDF Atom