[ruby-core:104472] [Ruby master Misc#17997] DevelopersMeeting20210715Japan
From:
merch-redmine@...
Date:
2021-07-02 15:38:39 UTC
List:
ruby-core #104472
Issue #17997 has been updated by jeremyevans0 (Jeremy Evans). * [Feature #15856] Performance of redundant `Kernel.require` is slow when many gems are activated (jeremyevans0) * Repeated require of native library without extension is very slow. * Repeated require of pure ruby library without extension is fast. * Making `search_required` use the same logic for both native and pure ruby libraries makes repeated require of native library without extension fast. * In addition to dramatically increasing the performance, this also makes the behavior consistent for native and pure ruby libraries. * This breaks backwards compatibility, in that `require 'foo.so'; require 'foo'` will not load `foo.rb` if it exists. * Is such breakage acceptable for the dramatically increased performance and increased consistency? * [Feature #17724] Make the pin operator support instance/class/global variables (jeremyevans0) * Is it OK to allow the pattern matching pin operator to directly support instance/class/global variables? * [Bug #17757] Hash#slice does not keep compare_by_identity on the results (jeremyevans0) * Some hash methods do not consistently return hashes with compare by identity flag if receiver has compare by identity flag. * Some of these are definitely bugs, as they treat the empty receiver differently than non empty receiver. * However, do we want change the behavior for `slice` and/or `transform_keys` to return compare by identity hash if receiver has compare by identity flag? * [Bug #17737] `Array#permutation` does not immediately check the arity when no block is given (jeremyevans0) * If we think this is a bug, we'll have to move all argument checking before enumerator creation in all of the methods that return enumerator. * I don't think it is a bug. * If this isn't a bug, can this be closed? * [Bug #17719] Irregular evaluation order in hash literals (jeremyevans0) * Should we fix the evaluation order for duplicate hash keys using @nobu's patch (my preference)? * Or should we change duplicate hash keys from a warning to an error? ---------------------------------------- Misc #17997: DevelopersMeeting20210715Japan https://bugs.ruby-lang.org/issues/17997#change-92731 * Author: mame (Yusuke Endoh) * Status: Open * Priority: Normal ---------------------------------------- # The next dev meeting **Date: 2021/07/15 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. ``` - It is recommended to add a comment by 2021/07/12. 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: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>