[#100689] [Ruby master Feature#17303] Make webrick to bundled gems or remove from stdlib — hsbt@...
Issue #17303 has been reported by hsbt (Hiroshi SHIBATA).
11 messages
2020/11/02
[#100852] [Ruby master Feature#17326] Add Kernel#must! to the standard library — zimmerman.jake@...
SXNzdWUgIzE3MzI2IGhhcyBiZWVuIHJlcG9ydGVkIGJ5IGpleiAoSmFrZSBaaW1tZXJtYW4pLg0K
24 messages
2020/11/14
[#100930] [Ruby master Feature#17333] Enumerable#many? — masafumi.o1988@...
Issue #17333 has been reported by okuramasafumi (Masafumi OKURA).
10 messages
2020/11/18
[#101071] [Ruby master Feature#17342] Hash#fetch_set — hunter_spawn@...
Issue #17342 has been reported by MaxLap (Maxime Lapointe).
26 messages
2020/11/25
[ruby-core:100699] [Ruby master Misc#17299] DevelopersMeeting20201120Japan
From:
merch-redmine@...
Date:
2020-11-02 20:45:34 UTC
List:
ruby-core #100699
Issue #17299 has been updated by jeremyevans0 (Jeremy Evans). * [Feature #17143] Improve support for warning categories (jeremyevans0) * I researched the Python warning categories, and provided some analysis. * Can we decide on warning categories so they can be implemented in time for Ruby 3? * [Bug #10845] Subclassing String (jeremyevans0) * In #6087, matz decided that in Ruby 3.0, methods for Array subclasses should return arrays and not subclass instances. * The same issues that apply to Array subclasses also apply to String subclasses. * Do we want to make String subclass methods return strings instead of subclass instances? * If so, is the pull request OK? * Note that changing the behavior of String methods will require changes in Rails. * [Bug #11022] opening an eigenclass does not change the class variable definition context (jeremyevans0) * This was discussed in the December 2019 meeting, but a decision was not made. * Considering #14012 was rejected last meeting, can we also reject this? * [Bug #7844] include/prepend satisfiable module dependencies are not satisfied (jeremyevans0) * This was discussed in the December 2019 meeting, but a decision was not made. * Considering the other improvements to include/prepend in 3.0, it would be a good time to fix this. * [Bug #11213] defined?(super) ignores respond_to_missing? (jeremyevans0) * I agree with Koichi that it is best to accept the current behavior as spec. * Can we reject this? ---------------------------------------- Misc #17299: DevelopersMeeting20201120Japan https://bugs.ruby-lang.org/issues/17299#change-88339 * Author: mame (Yusuke Endoh) * Status: Open * Priority: Normal ---------------------------------------- # The next dev meeting **Date: 2020/11/20 13:00-17:00** Place/Sign-up/Agenda/Log: *TBD* - Dev meeting *IS NOT* a decision-making place. All decisions should be made on 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 cannot attend, a different attendee can ask instead of you (if the attendee can understand your issue). - We will write a log about the discussion in a file or on 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' time. - *DO NOT* discuss them on this ticket, please. # Call for agenda items If you have a ticket that you want Matz and other committers to discuss, please post it on 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 points 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's discuss this feature. ``` - Comment deadline: 2020/11/13 (one week before the meeting) - The format is strict. We'll use [this script to automatically create a markdown-style agenda](https://gist.github.com/mame/b0390509ce1491b43610b9ebb665eb86). We may ignore comments that do not follow the format. - Your comment is mandatory. We cannot read the entire discussion of the ticket within a limited time. -- https://bugs.ruby-lang.org/ Unsubscribe: <mailto:[email protected]?subject=unsubscribe> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>