From: merch-redmine@... Date: 2019-09-08T15:49:46+00:00 Subject: [ruby-core:94845] [Ruby master Misc#16152] DevelopersMeeting20190919Japan Issue #16152 has been updated by jeremyevans0 (Jeremy Evans). * [Bug #12984] `rescue *[]` should be equivalent to `rescue` as `method_call(*[])` is equivalent to `method_call` * I think the current behavior is expected. Can matz confirm? * [Bug #11022] opening an eigenclass does not change the class variable definition context * I think the current behavior is expected. Can matz confirm? * [Bug #8297] extend & inherited class variable issue * I would like to fix Module#class_variables to be consistent with Module#class_variable_get using the patch. * [Bug #7844] include/prepend satisfiable module dependencies are not satisfied * I would like to make it so Module#include does not prepend modules before the receiver using the patch. * [Bug #7522] Non-core "Type()" Kernel methods return new object * I would like to make it so Kernel#{BigDecimal,Complex,Pathname} return argument if given correct type using the patch. * [Bug #11636] super in instance_eval in a method defined in a module is invoked with a wrong receiver * I would like to raise an exception instead, similar to super in instance_eval in method defined in class using the patch. ---------------------------------------- Misc #16152: DevelopersMeeting20190919Japan https://bugs.ruby-lang.org/issues/16152#change-81468 * Author: mame (Yusuke Endoh) * Status: Open * Priority: Normal * Assignee: ---------------------------------------- Please comment on your favorite ticket numbers you want to ask to discuss with your *SHORT* comment or summary. (your summary/comment will help us because we don't need to read all of the ticket comments) *DO NOT* discuss then on this ticket, please. ---- Date: 2019/09/19 (Thu) Time: 13:00-17:00 (JST) Place: (Written in the Log) Sign-up: (Add your name in the Log) Log: https://docs.google.com/document/d/1oYWVhH6BEgTNy8PxMUd-MS3JUK0kQMw43q5saBp8aZk # NOTES - 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 log about the discussion to a 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 are scheduled according to when/where we can reserve Matz's time. # Agenda ## Next dev-meeting ## About 2.7 timeframe ## Check security tickets ## Discussion ---- Please comment on your favorite ticket we need to discuss with *the following format*. ``` * [Ticket ref] Ticket title (your name) * your comment why you want to put this ticket here if you want to add. ``` Your comment is very important if you are no attendee because we can not ask why you want to discuss it. 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. ``` We don't guarantee to put tickets in the agenda if the comment violates the format (because it is hard to copy&paste). **A short summary of a ticket is strongly recommended. We cannot read all discussion of the ticket in a limited time.** A proposal is often changed during the discussion, so it is very helpful to summarize the latest/current proposal, post it as a comment in the ticket, and write a link to the comment. -- https://bugs.ruby-lang.org/ Unsubscribe: