From: merch-redmine@... Date: 2021-03-05T18:34:15+00:00 Subject: [ruby-core:102748] [Ruby master Misc#17635] DevelopersMeeting20210317Japan Issue #17635 has been updated by jeremyevans0 (Jeremy Evans). * [Bug #11335] `ruby -r debug` catchpoint problem (jeremyevans0) * This support is broken since Ruby 2.0. * The debug library has no tests, and I'm guessing minimal usage. * Can we remove debug from stdlib in Ruby 3.1? * Alternatively, do we want to rewrite debug to use TracePoint instead of set_trace_func? * [Bug #17354] Module#const_source_location is misleading for constants awaiting autoload (jeremyevans0) * Currently, Module#const_source_location returns autoload location and not definition location, which seems wrong. * It could return `[]`, similar to constants defined in C where we don't know the location. * It could trigger the autoload, and then return the definition location. * Which behavior is desired for Module#const_source_location? * Related, should Module#const_defined? trigger autoload instead of assuming the constant is defined? * [Bug #17164] Threads can ignore kill/interrupt/abort (jeremyevans0) * Basically, use of ensure/raise/rescue can make ruby unkillable without kill -9. * I think this behavior is expected. Can we confirm that? * [Bug #16996] Hash should avoid doing unnecessary rehash (jeremyevans0) * High performance code generally works around this by using Hash.[]. * Can we remove the rehashing in Hash#dup and #clone? * [Bug #16908] Strange behaviour of Hash#shift when used with `default_proc`. (jeremyevans0) * Currently, Hash#shift calls the default proc with nil if the hash is empty and the hash has a default proc, and returns only the value. * This is similar to when the hash has a default value, where only the default value is returned if the hash is empty. * I think this behavior is expected. Can we confirm that? ---------------------------------------- Misc #17635: DevelopersMeeting20210317Japan https://bugs.ruby-lang.org/issues/17635#change-90760 * Author: mame (Yusuke Endoh) * Status: Open * Priority: Normal ---------------------------------------- # The next dev meeting **Date: 2021/03/17 13:00-17:00** Place/Sign-up/Agenda/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 log about the discussion to a 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 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 2021/03/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](https://gist.github.com/mame/b0390509ce1491b43610b9ebb665eb86). 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. -- https://bugs.ruby-lang.org/ Unsubscribe: