From: "jeremyevans0 (Jeremy Evans)" Date: 2022-04-11T17:01:26+00:00 Subject: [ruby-core:108211] [Ruby master Misc#18652] DevMeeting-2022-04-21 Issue #18652 has been updated by jeremyevans0 (Jeremy Evans). * [Bug #18628] Link contributing is broken (jeremyevans0) * Also affects #18665. Problem is that ruby uses the --page-dir rdoc option. * Any documentation generation that does not use the --page-dir rdoc option has broken links. * I propose to remove the --page-dir rdoc option, and fix any internal documentation that relies on it. * This will allow externally generated documentation (which is unlikely to use --page-dir) to have working links. * [Bug #18155] (nil..nil).cover?(x) is true for all x since beginless ranges were introduced (jeremyevans0) * How should cover? work for ranges unbounded in both directions? * In 2.7, with the introduction of beginless ranges, it started always returning true, instead of returning false. * I propose to reject this bug, and keep the current behavior. * [Bug #18629] block args array splatting assigns to higher scope _ var (jeremyevans0) * I believe this is expected behavior. Can we confirm that and reject this bug? * [Bug #18622] const_get still looks in Object, while lexical constant lookup no longer does (jeremyevans0) * Can we decide whether const_get should operate like a relative lookup or an absolute lookup? * Currently, it operates as a relative lookup, so `Array.const_get(:String)` is like `class Array; String; end` and works. * If switched to an absolute lookup, `Array.const_get(:String)` would be like `Array::String`, and would raise an exception. * [Bug #18649] Enumerable#first breaks out of the incorect block when across threads (jeremyevans0) * Can we specify how Enumerator#first should work across threads? * It currently has definitely incorrect behavior, jumping out of block it should not jump out of. * I have a patch that fixes the definitely incorrect behavior, but still passes a value to the calling thread, which may be undesireable. ---------------------------------------- Misc #18652: DevMeeting-2022-04-21 https://bugs.ruby-lang.org/issues/18652#change-97195 * Author: mame (Yusuke Endoh) * Status: Open * Priority: Normal ---------------------------------------- # The next dev meeting **Date: 2022/04/21 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/04/18. 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: