From: merch-redmine@... Date: 2020-12-02T21:42:51+00:00 Subject: [ruby-core:101208] [Ruby master Misc#17346] DevelopersMeeting20201210Japan Issue #17346 has been updated by jeremyevans0 (Jeremy Evans). * [Feature #17055] Allow suppressing uninitialized instance variable and method redefined verbose mode warnings (jeremyevans0) * Can we completely remove uninitialized instance variable warnings? Then we don't need this feature. I would very much like that in Ruby 3. * [Bug #17280] Dir.glob with FNM_DOTMATCH matches ".." and "." and results in duplicated entries (jeremyevans0) * Do we want to change the behavior to exclude ".." and duplicate results? * If so, is the pull request acceptable? * [Bug #17162] Dir['**/*'] : stack smashing detected when listing big amount of directories (jeremyevans0) * Do we want to add an internal recursion limit to try to prevent this? * [Bug #17218] Range#step sometimes behaves unexpectedly with Rational endpoints and increment (jeremyevans0) * This is caused by calling `rb_int_*` functions directly instead of Ruby methods. * Do we want to switch `arith_seq_last` to using Ruby methods, and if so, should all of the `rb_int_*` be switched, or just the minimal number? * The pull request only changes three of the `rb_int_*` to `rb_funcall`, is it OK? * [Bug #13663] `String#upto` doesn't work as expected (jeremyevans0) * I think the current behavior of `String#upto` in this case is expected and not a bug. * Is it OK to close this? ---------------------------------------- Misc #17346: DevelopersMeeting20201210Japan https://bugs.ruby-lang.org/issues/17346#change-88892 * Author: mame (Yusuke Endoh) * Status: Open * Priority: Normal ---------------------------------------- # The next dev meeting **Date: 2020/12/10 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/12/03 (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: