From: "jeremyevans0 (Jeremy Evans)" Date: 2021-11-08T18:01:00+00:00 Subject: [ruby-core:105970] [Ruby master Misc#18266] DevelopersMeeting20211118Japan Issue #18266 has been updated by jeremyevans0 (Jeremy Evans). * [Feature #6210] load should provide a way to specify the top-level module (jeremyevans0) * This is fairly easy to implement in a backwards compatible manner, and seems useful. * Are we OK adding this feature? If so, is the pull request acceptable? * [Feature #11256] anonymous block forwarding (jeremyevans0) * This was accepted by @matz four years ago, but never committed. * I've created a new working version based on patches from @nobu and @mame. * There should be no backwards compatibility issues, as the proposed syntax is currently invalid. * Is it OK to add this feature? If so, is the pull request acceptable? * [Feature #11689] Add methods allow us to get visibility from Method and UnboundMethod object. (jeremyevans0) * As requested by @matz, I put together a patch for #public?, #private?, and #protected?. * Do we want to use this approach, or do we want to reconsider the #visibility method that returns a symbol? * If we want to use this approach, is the pull request acceptable? * [Feature #12495] Make "private" return the arguments again, for chaining (jeremyevans0) * This seems useful, and the backwards compatible issues are quite small. * Are we OK adding this feature? If so, is the pull request acceptable? * [Feature #16663] Add block or filtered forms of Kernel#caller to allow early bail-out (jeremyevans0) * Currently it is not possible to generate a partial backtrace without knowing how many frames you need up front. * This feature allows the production of partial backtraces without that knowledge. * For example, you can use it to return the only the first frame that meets some criteria. * There shouldn't be any backwards compatibility issues, as caller/caller_locations does not currently use a block. * Are we OK adding this feature? If so, is the pull request acceptable? ---------------------------------------- Misc #18266: DevelopersMeeting20211118Japan https://bugs.ruby-lang.org/issues/18266#change-94517 * Author: mame (Yusuke Endoh) * Status: Open * Priority: Normal ---------------------------------------- # The next dev meeting **Date: 2021/11/18 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/11/15. 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: