Misc #16152



Added by mame (Yusuke Endoh) over 3 years ago. Updated over 3 years ago.



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)


  • 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.


Next dev-meeting

About 2.7 timeframe

Check security tickets


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.


* [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.

Related issues 1 (1 open0 closed)

Related to Ruby master - Misc #14770: [META] DevelopersMeetingOpenActions
Actions #1

Updated by mame (Yusuke Endoh) over 3 years ago

  • Related to Misc #14770: [META] DevelopersMeeting added
Actions #2

Updated by mame (Yusuke Endoh) over 3 years ago

  • Description updated (diff)

Updated by jeremyevans0 (Jeremy Evans) over 3 years ago

  • [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.

Updated by Eregon (Benoit Daloze) over 3 years ago

  • [Feature #16150] Add a way to request a frozen string from to_s

Updated by mame (Yusuke Endoh) over 3 years ago

  • [Bug #16154] lib/delegate.rb issues keyword argument warnings
    • Module#pass_positional_hash for disabling false positive warnings in delegation. This is just for 2.7 migration path. Can we commit this?

Updated by methodmissing (Lourens Naudé) over 3 years ago

  • [Misc #16124] Let the transient heap belong to objspace (methodmissing)
    • As per PR and outline of pros and cons in the issue, I think it's stable and performance enough to be coupled a little tighter to objspace instead of just being a global slab / scratch space. Thoughts?
    • I volunteer to do the work, if it makes sense.
    • Also VM -> global method cache for example - cleaner for multi-VM, but not sure of the future of MVM

Updated by methodmissing (Lourens Naudé) over 3 years ago

  • [Misc #16160] Lazy init thread local storage (methodmissing)
    • Storage for Fiber local storage of execution context for Thread#[] and Thread#[]= APIs are lazy initialized.
    • I think the same pattern should be applied to real thread local storage as well.

Updated by alanwu (Alan Wu) over 3 years ago

  • [Feature #16131] Remove $SAFE, taint and trust
  • What do you think about the proposed schedule?
  • I am asking because this might inform the fix for [Bug #16151]
  • [Feature #16123] Allow calling a private method with self.
  • Pinging because of inactivity. I think it makes sense.

Patches that would benefit from reviews:

  • [Bug #16121] Stop making a redundant hash copy in Hash#dup
  • [Feature #16163] Reduce the output of RubyVM::InstructionSequence#to_binary
  • [Bug #16119] Optimize Array#flatten and flatten! for already flattened arrays

Updated by connorshea (Connor Shea) over 3 years ago

  • [Feature #16155] Add an Array#intersection method
    • Is this an acceptable method name?
    • Should this be a simple alias for Array#&, or should it accept multiple arrays as arguments, like difference and union do?

Updated by jeremyevans0 (Jeremy Evans) over 3 years ago

  • [Feature #16168] Add keyword argument separation to C functions using rb_scan_args
    • I would like to commit the patch so that methods implemented in C handle keyword argument separation similar to methods implemented in Ruby.

Updated by hsbt (Hiroshi SHIBATA) over 3 years ago

[Feature #16170] Remove the unmaintained libraries from Ruby 2.7

  • Is it ok to remove them?

Updated by Dan0042 (Daniel DeLorme) over 3 years ago

  • [Feature #16120] Omitted block argument if block starts with dot-method call
    •{ } has beautiful readability, no incompatibility, changes a syntax error into an intuitive idiom, already implemented in 6 lines by nobu. 本当に美しいと思います。
  • [Feature #16153] eventually_frozen flag to gradually phase-in frozen strings
    • This would make previous backward-incompatible proposals (#16150, #15836, #11473) possible with a backward-compatible transition.
  • [Feature #16021] floor/ceil/round/truncate should accept a :step argument
    • Since Time#floor/ceil methods were added, it would be convenient to round to the previous/next minute/hour: Also add to Numeric, for convenience and consistency.
    • If this is a good idea I would like to try writing it.

Updated by shyouhei (Shyouhei Urabe) over 3 years ago

[Misc #16172] C++ situation?

  • What do we do with C++ extensions?

Updated by shyouhei (Shyouhei Urabe) over 3 years ago

Can someone update the "Log" link above?

Updated by mame (Yusuke Endoh) over 3 years ago

  • Status changed from Open to Closed

I published the Log. Closing.


Also available in: Atom PDF