From: "jeremyevans0 (Jeremy Evans) via ruby-core" Date: 2023-07-06T18:20:40+00:00 Subject: [ruby-core:114101] [Ruby master Misc#19722] DevMeeting-2023-07-13 Issue #19722 has been updated by jeremyevans0 (Jeremy Evans). * [Bug #11064] #singleton_methods for objects with special singleton_class returns an empty array (jeremyevans0) * Is it OK to make {NilClass,TrueClass,FalseClass}#singleton_method always raise an exception? * [Bug #19293] The new Time.new(String) API is nice... but we still need a stricter version of this (jeremyevans0) * It was apparently decided that `Time.new("2023-01")` and similar should raise an exception in 3.2.1, but that didn't happen. * Do we want to raise an exception in this case and similar cases, and backport the changes to Ruby 3.2.3? * [Bug #19749] Confirm correct behaviour when attaching private method with `#define_method` (jeremyevans0) * Currently, `#define_method` does not change visibility when defining a method using the same body as it currently has. * This seems like an oversight and not intentional behavior, can we fix it? * [Bug #19726] Script loadde twice when requiring self (jeremyevans0) * Do we want to add the full path of the main script to `$LOADED_FEATURES` to prevent it from being loaded again if required? * [Bug #19544] Custom quotes inconsistency (jeremyevans0) * Do we want to support whitespace characters as terminators for `%w` arrays? * I don't think it is worth making changes to support this. ---------------------------------------- Misc #19722: DevMeeting-2023-07-13 https://bugs.ruby-lang.org/issues/19722#change-103777 * Author: mame (Yusuke Endoh) * Status: Open * Priority: Normal ---------------------------------------- # The next dev meeting **Date: 2023/07/13 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 2023/07/10. 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/ ______________________________________________ ruby-core mailing list -- ruby-core@ml.ruby-lang.org To unsubscribe send an email to ruby-core-leave@ml.ruby-lang.org ruby-core info -- https://ml.ruby-lang.org/mailman3/postorius/lists/ruby-core.ml.ruby-lang.org/