From: merch-redmine@... Date: 2020-09-03T19:29:26+00:00 Subject: [ruby-core:99891] [Ruby master Misc#17138] DevelopersMeeting20200925Japan Issue #17138 has been updated by jeremyevans0 (Jeremy Evans). * [Feature #17143] Improve support for warning categories (jeremyevans0) * Warning.warn :category keyword support was approved last developer meeting. * I would like to add Kernel#warn :category keyword for Ruby-level warnings, and ruby_category_warn{,ing} for C-level warnings * I have prepared a pull request that adds them, and also adds categories for all core warnings. Is it OK? * [Bug #16518] Should we rationalize Rational's numerator automatically? (jeremyevans0) * I think we should make Kernel#Rational always return a Rational instance, or raise an exception if it cannot. * [Bug #15712] DateTime#=== should be defined and compare date and time instead of just the date (jeremyevans0) * DateTime#=== is currently the same as Date#===, but this seems more accidental than deliberate. * Do we want to define DateTime#=== and have it be similar to DateTime#==? * [Bug #15661] Disallow concurrent Dir.chdir with block (jeremyevans0) * Concurrently, we have a non-verbose warning. Do we want to switch to raising an exception? ---------------------------------------- Misc #17138: DevelopersMeeting20200925Japan https://bugs.ruby-lang.org/issues/17138#change-87423 * Author: mame (Yusuke Endoh) * Status: Open * Priority: Normal ---------------------------------------- # The next dev meeting **Date: 2020/09/25 13:00-17:00** 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. ``` - Comment deadline: 2020/09/18 (one week before the 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. -- https://bugs.ruby-lang.org/ Unsubscribe: