[#107867] Fwd: [ruby-cvs:91197] 8f59482f5d (master): add some tests for Unicode Version 14.0.0 — Martin J. Dürst <duerst@...>
To everybody taking care of continuous integration:
3 messages
2022/03/13
[#108090] [Ruby master Bug#18666] No rule to make target 'yaml/yaml.h', needed by 'api.o' — duerst <noreply@...>
Issue #18666 has been reported by duerst (Martin D端rst).
7 messages
2022/03/28
[#108117] [Ruby master Feature#18668] Merge `io-nonblock` gems into core — "Eregon (Benoit Daloze)" <noreply@...>
Issue #18668 has been reported by Eregon (Benoit Daloze).
22 messages
2022/03/30
[ruby-core:107899] [Ruby master Misc#18591] DevMeeting-2022-03-17
From:
"Eregon (Benoit Daloze)" <noreply@...>
Date:
2022-03-14 17:29:15 UTC
List:
ruby-core #107899
Issue #18591 has been updated by Eregon (Benoit Daloze). * [Bug #18632] Struct.new wrongly treats a positional Hash as keyword arguments (eregon) * Some C functions incorrectly treat a positional Hash as keyword arguments, e.g. Struct.new and Struct#initialize. * This is inconsistent with the separation of positional and keyword arguments in Ruby 3 * Jeremy proposed to audit and fix them * [Bug #18625] ruby2_keywords does not unmark the hash if the receiving method has a *rest parameter (eregon) * This seems a clear inconsistency, and it hurts for 3 reasons: * Can cause issues when migrating to other forms of delegation * Makes the ruby2_keywords semantics confusing/inconsistent/more complex * May force other Ruby implementations to replicate this bug if not fixed * I believe we should fix it now. Fixing it later would cause issues when migrating to `(*args, **kwargs)` or `(...)`. ---------------------------------------- Misc #18591: DevMeeting-2022-03-17 https://bugs.ruby-lang.org/issues/18591#change-96838 * Author: mame (Yusuke Endoh) * Status: Open * Priority: Normal ---------------------------------------- # The next dev meeting **Date: 2022/03/17 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/03/14. 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>