[#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:100708] [Ruby master Misc#17299] DevelopersMeeting20201120Japan
From:
muraken@...
Date:
2020-11-04 00:28:50 UTC
List:
ruby-core #100708
Issue #17299 has been updated by mrkn (Kenta Murata).
* [Feature #17291] Optimize `__send__` call
* Improve the performance of `__send__` call by the following ways
1. Omit emitting `__send__` calls for literal method name cases
2. Introduce a new instruction `sendsym` to skip `__send__` call for dynamic method name cases
* I guess it is no problem to skip `__send__` call because the following warning says "*redefining `__send__` may cause* ***serious problems***" for a long time
* I want to know Matz's reaction to this
----------------------------------------
Misc #17299: DevelopersMeeting20201120Japan
https://bugs.ruby-lang.org/issues/17299#change-88352
* 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>