From: "jeremyevans0 (Jeremy Evans)" Date: 2022-03-10T21:24:12+00:00 Subject: [ruby-core:107843] [Ruby master Misc#18591] DevMeeting-2022-03-17 Issue #18591 has been updated by jeremyevans0 (Jeremy Evans). * [Bug #18620] Not possible to partially curry lambda or proc's `call` method (jeremyevans0) * Should we make changes to allow this to work? It complicates the internals, and the benefits seem minimal. * If we do decide to make this change, I've prepared a patch, but the implementation is suboptimal. * [Feature #15357] Proc#parameters returns incomplete type information (jeremyevans0) * Last discussed at the March 2020 developer meeting, but no decision was made. * I still think it makes sense to consider a lambda keyword argument for Proc#parameters. * [Feature #12655] Accessing the method visibility (jeremyevans0) * This issue discusses many things that have been discussed previously in other issues. * I want to focus on one additional method: Module#undefined_instance_methods * We don't currently offer a way to see which methods are undefined in a module. * Is this worth adding? The use case I know of is it would allow significantly simpler implementation of the looksee gem. * [Bug #11063] Special singleton class should return true for singleton_class? test (jeremyevans0) * I don't think it is worth changing the existing behavior. * Can this be rejected? ---------------------------------------- Misc #18591: DevMeeting-2022-03-17 https://bugs.ruby-lang.org/issues/18591#change-96775 * Author: mame (Yusuke Endoh) * Status: Open * Priority: Normal ---------------------------------------- # The next dev meeting **Date: 2022/03/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 2022/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: