From: "jeremyevans0 (Jeremy Evans) via ruby-core" Date: 2023-10-05T21:24:39+00:00 Subject: [ruby-core:114953] [Ruby master Misc#19883] DevMeeting-2023-10-12 Issue #19883 has been updated by jeremyevans0 (Jeremy Evans). * [Feature #18573] Object#pack1 (jeremyevans0) * For the same reason as String#unpack1, saves an array allocation when packing a single object. * I think it would be useful to have this feature, but I prefer Array.pack1 to Object#pack1 to implement it. * Can we add this feature, and if so, do we want to use Array.pack1, Object#pack1, or a different method for it? * [Bug #19866] Future of `readline.rb` (jeremyevans0) * Seems odd for a standard library to attempt to load a non-standard library first, and fallback to loading a standard library. * Are we OK with how lib/readline.rb currently works? If so, we can close this. * [Bug #16927] String#tr won't return the expected result for some sign with diacritics (jeremyevans0) * Do we plan to convert String#tr (and potentially other String methods) from operating on codepoints to operating on grapheme clusters at some point? * [Bug #18903] Stack overflow signal handling seems to be triggered once and then not working after (jeremyevans0) * Should we raise fatal error instead of SystemStackError for stack overflows in C code? * VM stack overflow can be safely rescued, since we check for the stack overflow before overflowing. * C stack overflow cannot be safely rescued in all cases. ---------------------------------------- Misc #19883: DevMeeting-2023-10-12 https://bugs.ruby-lang.org/issues/19883#change-104825 * Author: mame (Yusuke Endoh) * Status: Open * Priority: Normal ---------------------------------------- # The next dev meeting **Date: 2023/10/12 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/10/09. 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/