[ruby-core:109436] [Ruby master Misc#18954] DevMeeting-2022-08-18
From:
"zverok (Victor Shepelev)" <noreply@...>
Date:
2022-08-06 13:37:06 UTC
List:
ruby-core #109436
Issue #18954 has been updated by zverok (Victor Shepelev). * [Feature #18368] `Range#step` semantics for non-`Numeric` ranges (zverok) * Proposal to reimplement `(a..b).step(c)` via `+`, or provide another method with this behavior * More clarifications provided & answers to the questions after last dev.meeting * [Bug #18580] `Range#include?` inconsistency for beginless String ranges * "This was discussed during the February 2022 developer meeting, and @matz said he needs more time to consider it." * [Feature #17330] `Object#non` (zverok) * Proposal to introduce generic "nullify if unacceptable" API (zverok) * more explanations and examples provided * [Feature #16122] `Struct::Value`: simple immutable value object (zverok) * **The ticket is in weird state. It has "Status: Feedback", but generic state "CLOSED", but I don't see any notice of HOW it was closed?..** Is it RedMine glitch?.. I don't see an option to reopen it. * The [latest comment](https://bugs.ruby-lang.org/issues/16122#note-28) from Matz seems to lean towards accepting proposal, the only culprit is a name: "Struct::Value seems acceptable to him, but he wanted to seek a better name. Devs suggested Tuple, NamedTuple, and Record, but none of them seemed to fit for him." * Can we somehow move forward with this? * [Feature #18934] Introduce method results memoization API in the core (zverok) * New ticket, proposing and justifying simple `memoized def method_without_args` ---------------------------------------- Misc #18954: DevMeeting-2022-08-18 https://bugs.ruby-lang.org/issues/18954#change-98589 * Author: mame (Yusuke Endoh) * Status: Open * Priority: Normal ---------------------------------------- # The next dev meeting **Date: 2022/08/18 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 2022/08/15. 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>