[ruby-core:113098] [Ruby master Misc#19525] DevMeeting-2023-04-13

Issue #19525 has been updated by jeremyevans0 (Jeremy Evans).


* [Bug #4040] SystemStackError with Hash[*a] for Large _a_ (jeremyevans0)
  * @ko1 fixed this issue for iseq methods accepting splats in Ruby 2.2.
  * We fixed this issue for cfunc methods in January.
  * I found this issue applies to all other method calls.
  * I developed a fix for all cases I could identity (yjit will need updates for it).
  * The fix results in a minor performance decrease in microbenchmarks.
  * I have attempted to offset this performance decrease with major optimizations to bmethod, send, symproc, and method_missing calls, using knowledge gained from fixing this bug.
  * Do we want to fix this issue, and if so, how much of a performance loss are we willing to accept?
  * I propose we should accept this fix if it doesn't result in more than 0.2% performance decrease in production benchmarks such as railsbench.
* [Bug #19533] Behavior of ===/include? on a beginless/endless range (nil..nil) changed in ruby 3.2 (jeremyevans0)
  * Do we want to make beginless+endless `Range#include?` return true for all objects?
  * A decision was made in August 2022 to have `include?` raise exception for beginless/endless ranges.
  * Looking back, it's possible that it was desired for the beginless^endless case and not the beginless+endless case.
* [Bug #19564] Range.cover? fails for Range wrapped in SimpleDelegator (jeremyevans0)
  * Do we want to handle delegate objects in `Range#cover?`?
  * If so, do we want to add `Range#to_range` and have `Range#cover?` check for that method and call it if it exists?
* [Feature #19573] Add Class#singleton_inherited (jeremyevans0)
  * This would be similar to `Class#inherited`, but called for singleton class creation instead of normal subclass creation.
  * This could be used to warn or raise on singleton class creation, or modify the object to change behavior.


----------------------------------------
Misc #19525: DevMeeting-2023-04-13
https://bugs.ruby-lang.org/issues/19525#change-102633

* Author: mame (Yusuke Endoh)
* Status: Open
* Priority: Normal
----------------------------------------
# The next dev meeting

**Date: 2023/04/13 13:00-17:00** (JST)
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 record of the discussion in the 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 of the meeting 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 2023/04/10. 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/
 ______________________________________________
 ruby-core mailing list -- [e-mail]
 To unsubscribe send an email to [e-mail]
 ruby-core info -- https://ml.ruby-lang.org/mailman3/postorius/lists/ruby-core.ml.ruby-lang.org/