From: "jeremyevans0 (Jeremy Evans)" Date: 2022-01-03T18:22:43+00:00 Subject: [ruby-core:106955] [Ruby master Misc#18399] DevMeeting-2022-01-13 Issue #18399 has been updated by jeremyevans0 (Jeremy Evans). * [Bug #15928] Constant declaration does not conform to JIS 3017:2013 (jeremyevans0) * This was discussed at the May 2021 developer meeting, and it was decided to wait until after 3.1. * This makes constant assignment consistent with attribute assignment, so evaluation occurs left-to-right. * Is this OK to commit now? * [Bug #17545] Calling dup on a subclass of Proc returns a Proc and not the subclass (jeremyevans0) * Is this OK to commit this now? * [Bug #16908] Strange behaviour of Hash#shift when used with `default_proc`. (jeremyevans0) * This was discussed in the March 2021 developer meeting, and it was decided to wait until after 3.1. * I've added a pull request to make `Hash#shift` return nil if the hash is empty. * Is this OK to commit this now? * [Bug #16663] Add block or filtered forms of Kernel#caller to allow early bail-out (jeremyevans0) * @headius prefers iteration over search, and recommends `Thread.each_backtrace` as the method name. * @headius also has an idea for a block form that returns an enumerable, but I think that would greatly increase complexity. * I don't think `each_backtrace` is a good name for a method that yields individual caller locations. * I would like to go forward with `Thread.each_caller_location` or `Kernel.each_caller_location` (singleton method only), yielding `Thread::Backtrace::Location` objects. Is that acceptable? * [Bug #11064] #singleton_methods for objects with special singleton_class returns an empty array (jeremyevans0) * It is a bit inconsistent that `singleton_method` for `nil`/`true`/`false` returns a Method, but `singleton_methods` does not include the method. * Is this a bug, or expected behavior? ---------------------------------------- Misc #18399: DevMeeting-2022-01-13 https://bugs.ruby-lang.org/issues/18399#change-95778 * Author: mame (Yusuke Endoh) * Status: Open * Priority: Normal ---------------------------------------- # The next dev meeting **Date: 2022/01/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 2022/01/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](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: