From: merch-redmine@... Date: 2020-06-04T15:39:40+00:00 Subject: [ruby-core:98655] [Ruby master Misc#16933] DevelopersMeeting20200618Japan Issue #16933 has been updated by jeremyevans0 (Jeremy Evans). * [Bug #9573] descendants of a module don't gain its future ancestors, but descendants of a class, do (jeremyevans0) * Support for Module#include was implemented 3 months ago * Bugs prevented support for Module#prepend at the time * I've since fixed all bugs * Implementing support for Module#prepend is now straightforward and causes no test failures, is it OK to merge the patch? * [Feature #14267] Lazy proc allocation introduced in #14045 creates regression (jeremyevans0) * I added a patch implementing Proc#== and #eql? (previously not implemented, so Object#== and #eql? were used) * Do the equalivance conditions I describe make sense, or should more be added? * Is it OK to merge the patch? * [Bug #11669] inconsitent behavior of refining frozen class (jeremyevans0) * Refining a frozen class where the refinement adds a method is currently broken. * Refinement methods are internal, so I'm not sure we should raise FrozenError in this case * Is it OK to merge the patch? * [Bug #16504] `foo(*args, &args.pop)` should pass all elements of args (jeremyevans0) * Bug is due to an optimization that skips duping of args for the splat. * I created a patch that fixes the issue in most cases by removing the optimization in those cases. * The patch does not remove the optimization in common cases, such as `&local_variable` or `&:symbol` * Truly fixing the issue in all cases requires removing the optimization completely. * Is it OK to merge the patch? * [Feature #16470] Issue with nanoseconds in Time#inspect (jeremyevans0) * Currently, Time#inspect can display fractional seconds as a rational, which few rational people want. * I think Time#inspect should always display fractional seconds as decimal. * I have a patch to do this, but it makes Time#inspect the same for Time instances that are not equal. * Arbitrary precision for fractional seconds, the benefit of storing nanoseconds as a rational, seems pointless to me. * Do we want to keep things as is, merge the patch, or change Time's implementation so fractional seconds are not stored with greater than nanosecond precision? ---------------------------------------- Misc #16933: DevelopersMeeting20200618Japan https://bugs.ruby-lang.org/issues/16933#change-85986 * Author: mame (Yusuke Endoh) * Status: Open * Priority: Normal ---------------------------------------- # The next dev meeting **Date: 2020/06/18 13:00-17:00** Place/Agenda/Log: https://github.com/ruby/dev-meeting-log/blob/master/DevelopersMeeting20200618Japan.md - 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. - *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. ``` - Comment deadline: 2020/06/11 (one week before the 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. -- https://bugs.ruby-lang.org/ Unsubscribe: