From: "jeremyevans0 (Jeremy Evans)" Date: 2021-11-29T16:59:29+00:00 Subject: [ruby-core:106315] [Ruby master Misc#18346] DevelopersMeeting20211209Japan Issue #18346 has been updated by jeremyevans0 (Jeremy Evans). * [Feature #18351] Support anonymous rest and keyword rest argument forwarding (jeremyevans0) * I think this is a natural addition after the addition of anonymous block forwarding in #11256. * Is it OK to support this syntax? If so, is the patch acceptable? * [Feature #16663] Add block or filtered forms of Kernel#caller to allow early bail-out (jeremyevans0) * Two possible method names are find_caller and each_caller. * find_caller optimizes for the case where the first matching frame will be returned. * each_caller is more general, always iterating unless there is a non-local exit (break/return). * Are either of these names acceptable? If so, which method name should be used? * [Feature #12084] `Class#instance` (jeremyevans0) * This should be simple to implement, since a singleton class keeps a reference to the instance. * Are we OK adding this feature? If so, is the method name acceptable, or do we want `singleton_instance`? * If called on a non-singleton class, should TypeError be raised? * For TrueClass, FalseClass, and NilClass, should it return true, false, and nil? * [Bug #14891] Pathname#join has different behaviour to File.join (jeremyevans0) * I agree with @znz that this behavior is expected. * Can this be closed? * [Bug #14434] IO#reopen fails after EPIPE (jeremyevans0) * I'm not sure whether this behavior is a bug. * The behavior has existed since Ruby 1.9 (no failure in 1.8.7). * Can we decide whether this behavior is expected or a bug? ---------------------------------------- Misc #18346: DevelopersMeeting20211209Japan https://bugs.ruby-lang.org/issues/18346#change-94942 * Author: mame (Yusuke Endoh) * Status: Open * Priority: Normal ---------------------------------------- # The next dev meeting **Date: 2021/12/09 13:00-17:00** (JST) 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/12/06. 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: