From: "jeremyevans0 (Jeremy Evans)" Date: 2022-10-10T16:27:52+00:00 Subject: [ruby-core:110249] [Ruby master Misc#19040] DevMeeting-2022-10-20 Issue #19040 has been updated by jeremyevans0 (Jeremy Evans). * [Bug #19033] One-liner pattern match as Boolean arg syntax error (jeremyevans0) * `m(a in b)` is syntax error, similar to how `m(a if b)` is a syntax error * `m a in b` is a syntax error, but `m a if b` is not (parsed as `m(a) if b`) * `m((a in b))` and `m((a if b))` are both valid syntax * Should we attempt to support `m(a in b)`, `m(a if b)`, and/or `m a in b`? * [Bug #18998] Kernel#Integer does not convert SimpleDelegator object expectly (jeremyevans0) * I think this behavior is expected and not a bug. * Should core methods attempt to deal specially with objects using stdlib delegate library? * [Bug #18983] Range#size for beginless Range is not nil. (jeremyevans0) * `(..object).size` returns Infinity and `(object..).size` returns nil for non-numeric objects * Should we change `(..object).size` to return nil instead of Infinity? * [Bug #18797] Third argument to Regexp.new is a bit broken (jeremyevans0) * This was discussed in the August 2022 developer meeting, but there was confusion about whether the third argument is ignored or used. * @matz thought the third argument was ignored, but it is used and results in unexpected behavior. * Should I update the documentation, or should the third argument be deprecated and removed? ---------------------------------------- Misc #19040: DevMeeting-2022-10-20 https://bugs.ruby-lang.org/issues/19040#change-99538 * Author: mame (Yusuke Endoh) * Status: Open * Priority: Normal ---------------------------------------- # The next dev meeting **Date: 2022/10/20 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/10/17. 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: