[ruby-core:114408] [Ruby master Misc#19766] DevMeeting-2023-08-24
From:
"jeremyevans0 (Jeremy Evans) via ruby-core" <ruby-core@...>
Date:
2023-08-18 16:47:27 UTC
List:
ruby-core #114408
Issue #19766 has been updated by jeremyevans0 (Jeremy Evans). * [Bug #19779] `eval "return"` at top level raises `LocalJumpError` (jeremyevans0) * Do we want to allow `eval "return"` at top level with the same sematics as `return`? * [Bug #19749] Confirm correct behaviour when attaching private method with `#define_method` (jeremyevans0) * This was discussed last month, but discussion focused on the general semantics and not the specific bug I want to fix. * Please see comments #13 and #15 for examples of the bug I want to fix. Can we fix that specific bug? * [Bug #19829] Enumerator.product called with keyword arguments raises exception with not precise message (jeremyevans0) * Can we add rb_no_keywords_accepted to the C-API, so that C functions can implement the equivalent of **nil? * [Misc #19740] Block taking methods can't differentiate between a non-local return and a throw (jeremyevans0) * The underlying issue is no longer a problem after a fix to timeout to always use raise instead of throw. * However, do we want to add a feature for ensure blocks to know if they were called via throw? * I'm against such a feature, as I don't think we want libraries treating throw differently than other non-local return. ---------------------------------------- Misc #19766: DevMeeting-2023-08-24 https://bugs.ruby-lang.org/issues/19766#change-104158 * Author: mame (Yusuke Endoh) * Status: Open * Priority: Normal ---------------------------------------- # The next dev meeting **Date: 2023/08/24 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/08/21. 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/