From: "jeremyevans0 (Jeremy Evans) via ruby-core" Date: 2024-03-04T18:39:47+00:00 Subject: [ruby-core:117055] [Ruby master Misc#20281] DevMeeting-2024-03-14 Issue #20281 has been updated by jeremyevans0 (Jeremy Evans). * [Bug #20301] `Set#add?` does two hash look-ups (jeremyevans0) * This doesn't seem like a bug to me, as there was never a guarantee of a single hash lookup. * Fixed proposed is adding Hash#exchange_value and using it. * Alternative fix would be adding block support to Hash#store, yielding existing value if already set (similar to Hash#update). * Adding/modifying Hash just for Set seems undesirable, especially as I would like to rewrite Set in C as a core class. * [Bug #19231] Integer#step and Float::INFINITY - inconsistent behaviour when called with and without a block (jeremyevans0) * If receiver and step are both integers and end value is a float, can we change to always yielding integers? * Alternatively, we could just tell users to use `nil` instead of `Float::INFINITY` for the end value. ---------------------------------------- Misc #20281: DevMeeting-2024-03-14 https://bugs.ruby-lang.org/issues/20281#change-107130 * Author: mame (Yusuke Endoh) * Status: Open ---------------------------------------- # The next dev meeting **Date: 2024/03/14 09:00-12:00, 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 2024/03/11. 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 -- ruby-core@ml.ruby-lang.org To unsubscribe send an email to ruby-core-leave@ml.ruby-lang.org ruby-core info -- https://ml.ruby-lang.org/mailman3/postorius/lists/ruby-core.ml.ruby-lang.org/