Misc #20336: DevMeeting-2024-04-17

• Status: Closed
• Assignee: -

[mame (Yusuke Endoh)]

The next dev meeting

Date: 2024/04/17 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 2024/04/14. 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 #20300] Hash: set value and get pre-existing value in one call (eregon)
  • It seems generally useful (see latest comments there).
  • It is necessary for #20301 (as long as Set is implemented in Ruby, and I think it should).

[mame (Yusuke Endoh)]

• [Feature #19057] Hide implementation of rb_io_t
  • This change has broken our internal CI. Because our CI contributes to assure the quality of Ruby master, it is a shame that it will not work until the release of unicorn, which we do not know when (and whether) it will be released. I hope to postpone the change at least until unicorn etc. is released.

[matheusrich (Matheus Richard)]

• [Feature #5133] Array#unzip as an alias of Array#transpose

  • Seems a more friendly name for this method (easier if you don't have a strong math background)
  • It is nice that we can do an operation and reverse it with two similar-named methods:

    [1, 2, 3, 4].zip(["a", "b", "c", "d"], ["I", "II", "III", "IV"])
    # => [[[1, "a"], "I"], [[2, "b"], "II"], [[3, "c"], "III"], [[4, "d"], "IV"]]
    [[[1, "a"], "I"], [[2, "b"], "II"], [[3, "c"], "III"], [[4, "d"], "IV"]].unzip
    # => [[1, 2, 3, 4], ["a", "b", "c", "d"], ["I", "II", "III", "IV"]]
    

• [Feature #6413] Make Dir.entries default to Dir.entries(Dir.pwd)

  • Sounds like a reasonable default. I think there's no backward incompatibility.
  • Is there any significant different between doing Dir.entries(Dir.pwd) and Dir.entries(".")

[dentarg (Patrik Ragnarsson)]

• [Bug #19865] Segfault when calling user signal handlers during VM shutdown
  • Seems like the bug is well understood and there is a patch for it (https://github.com/nobu/ruby/tree/signal-at-cleanup), can it be merged?

[hsbt (Hiroshi SHIBATA)]

• [Feature #20347] Separate docs task from all
  • I would like to remove docs task from main. It works same as current behavior.
  • https://github.com/ruby/ruby/pull/10282/commits/b160083175aed062c320b8d76eafe1c8706309d4

[byroot (Jean Boussier)]

• [Feature #20396] Add string_value: true/false parameter to ObjectSpace.dump_all (byroot)
  • This method is often used in production to investigate memory leak and other memory related issues.
  • Because it dumps (pure ASCII) strings content, it may include personal identifiable information, secret keys, etc.
  • I'd like a mode that doesn't dump the string content to make it easier and safer to use in production.
  • I'd like to make this new mode the default to avoid mistakes. The backward compatibility concern should be minimal because string content is already optional.
• [Feature #20335] Thread.each_caller_location should accept the same arguments as caller and caller_locations (byroot)
  • When walking up the stack to find a specific frame, it's extremely common to want to skip the first one or two frames (see links in original issue), so I'd like an optional start argument.
  • @Eregon (Benoit Daloze) pointed that the length and range arguments wouldn't be useful, which I agree with, so perhaps they shouldn't be added.
• [Feature #18576] Change Encoding::ASCII_8BIT inspect representation to include BINARY (byroot)
  • Proposed patch: https://github.com/ruby/ruby/pull/10018
  • inspect returns "#<Encoding:BINARY (ASCII-8BIT)>"
  • (Encoding::CompatibilityError message is: "incompatible character encodings: BINARY (ASCII-8BIT) and EUC-JP"
  • No other changes.

[Eregon (Benoit Daloze)]

• [Feature #20350] Return chilled string from Symbol#to_s
  • Since there are now chilled strings, it seems the perfect tool to transition to Symbol#to_s eventually returning a frozen String to avoid wasteful allocations.
  • OK to return chilled strings for Symbol#to_s for 3.4?

[jeremyevans0 (Jeremy Evans)]

• [Bug #20325] Enumerator.product.size bug with zero * infinite enumerators (jeremyevans0)
  • This is working as documented, so I don't think it is a bug.
  • However, should the result of Enumerator.product be 0 if any argument is known to be empty?
• [Bug #20340] Ractor comments not applying to constant targets (jeremyevans0)
  • shareable_constant_value pragma is ignored for multiple assignment to constants.
  • Should it be respected?

[ioquatix (Samuel Williams)]

• [Bug #20414] Fiber#raise should recurse to resumed_fiber rather than failing.
  • Make Fiber#raise work even when the fiber is resuming another fiber.
  • Can we accept this change?
• [Feature #20215] Introduce IO#readable?
  • Can we accept this interface?

[segiddins (Samuel Giddins)]

• [Bug #20424] Zlib readpartial double allocations when reading into outbuf
  • Major source of allocations for rubygems & bundler
  • the linked PR fixes and has been open for a while, can we merge & ship it?

[hsbt (Hiroshi SHIBATA)]

• [Misc #20422] Bugfix release process
  • I would like to discuss about the current release workflow.

[mame (Yusuke Endoh)]

@matheusrich (Matheus Richard) Are you organizing old tickets? If so, I thank you for your activity, and would respectfully recommend that you aim to close/reject them in principle.
The fact that a proposal has remained undecided for a long time suggests that either not many people wanted the same feature or that the design still needs some consideration.
If you happened to want the feature in your daily Ruby programming and found an old ticket proposing the same feature, then no problem.
However, if you looked at an old ticket and just thought "this might be nice to have," it might be a good idea to wait until you actually encounter several situations where you would want the feature.
I feel that considering a proposal without someone who has actually experienced the need for the feature will not lead to a positive outcome.

[ufuk (Ufuk Kayserilioglu)]

• [Misc #20432] Proposal for workflow changes related to teeny releases (ufuk)
  • This is related to the agenda item proposed by @hsbt (Hiroshi SHIBATA) in https://bugs.ruby-lang.org/issues/20336#note-12
  • Can we discuss the proposals to make branch maintainers' lives easier, so that we can target 6-7 teeny releases per stable version per year?

[mame (Yusuke Endoh)]

• Status changed from Open to Closed

[matheusrich (Matheus Richard)]

@mame (Yusuke Endoh), I think I've been doing both things. Some things (like the rejected ticket for weighted samples) came from my own needs, while others were me trying to organize old tickets. I cannot reject/close tickets. Is there something I could do to help the core team close or invalidate old tickets?