May 2019 Meeting

calendar_today May 22, 2019 confirmation_number 19 tickets discussed Source English

DevMeeting-2019-05-22

Please comment 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 ticket comments)

DO NOT discuss then on this ticket, please.

Date: 2019/05/22 (Wed) Time: 13:00-17:00 (JST) Place: Speee Inc. (Tokyo, Japan) Sign-up: https://ruby.connpass.com/event/129507/

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 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 is scheduled according to when/where we can reserve Matz’s time.

Agenda

Next dev-meeting

About 2.7 timeframe

Check security tickets

Carry-over from previous meeting(s)

From Attendees

From non-attendees

Please comment 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 about 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 about this feature.

We don’t guarantee to put tickets in agenda if the comment violate the format (because it is hard to copy&paste).

Log

https://bugs.ruby-lang.org/issues/15782

Next Date

6/13 (Thu) 14:00-17:30 @ Speee

Ann

About 2.7 timeframe

  • Preview 1 soon? (in this week)

  • Waiting for Reline

  • Preview 2

  • no plan

Check security tickets

Nothing.

Topics

  • [Misc #14632] git.ruby-lang.org (k0kubun)

  • RUBY_REVISION should be full-length hash value

  • [Bug #15745] There is no symmetry in the beginless range and the endless range using Range#inspect (koic)(1..).inspect      #=> “1..”
  • (..5).inspect      #=> “..5”

  • (nil..nil).inspect #=> “nil..nil”

  • [Feature #14915] Deprecate String#crypt (jeremyevans0)

  • There are a few committers against the removal. They will reply into the ticket.

  • Jeremy Evans committer? -> “Go ahead” by matz (https://bugs.ruby-lang.org/issues/15853#change-78060, https://bugs.ruby-lang.org/issues/15839#change-78087)

  • [Feature #15765] [PATCH] Module#name without global constant search (alanwu)

  • Matz: leaf to nobu.

  • Nobu: Will check and merge.

  • [Feature #15772] Proposal: Add Time#ceil (osyo)

  • Shyouhei: Use case?

  • Matz: Okay!

  • [Feature #13645] Syntactic sugar for indexing when using the safe navigation operator (osyo)

  • Matz: the use case looks artificial. Reject once.

  • [Misc #15802] [PATCH] Reduce the minimum string buffer size from 127 to 63 bytes (methodmissing)

  • ko1 will check.

  • [Feature #14736] Thread selector for flexible cooperative fiber based concurrency (ioquatix)

  • (ko1, nobu, and matz talks)
  • Matz: I’m worry about the performance, it would be difficult to accept the patch as is. I’m not positive to add a hook to IO because it will bring a big overhead when buffered. I prefer auto-fiber to using traditional IOs with a hook.
  • Nobu: I’m negative to passing a FD. I agree with eregon.
  • Matz: Will reject.

  • Ko1: I’m unsure what design is best, but I think eregon wrote a good comment. It would be good that the proposal is much simpler than autofiber.

  • [Feature #15323] [PATCH] Proposal: Add Enumerable#filter_map (greggzst)

  • Matz will reply.

  • [Misc #15843] Make “trunk” a symbolic-ref of “master” on git.ruby-lang.org (k0kubun)

  • Go ahead?
  • Nobu: Why “master” is primary and “trunk” is secondary.

  • Akr: “Out of scope (for a short term)” is a trap! “accept” may mean accept for long term?

  • [Feature #15778] Expose an API to pry-open the stack frames in Ruby (eregon)

  • Ko1: I hate Binding.of_caller.

  • Shyouhei: How about requiring require “something” to communicate “should only be used for debugging”?

  • [Bug #7300] Hash#[] の挙動が 1.9.3 と異なっている (hsbt)

  • Mame: I’d like to merge it.

  • [Feature #14844] Future of RubyVM::AST?

  • What can we do about this? The current situation is confusing for everyone, the API sounds “blessed” by being in core but it’s actually experimental and unstable. Can we document it as clearly as possible when this API should be used? Could we improve the API so it’s less fragile to parser changes and could be reasonably implemented on other Ruby implementations?

  • “Add a document to warn the result of this API may (easily) change in future”

  • [Feature #15863] Add Hash#slice! and ENV.slice!(bogdanvlviv)

  • [Feature #15831] Add Array#extract, Hash#extract, and ENV.extract (bogdanvlviv)

  • Matz: negative. (Sorry I missed to log)

  • [Feature #15864] Proposal: Add methods to determine if it is an infinite range (osyo)

  • Matz: negative.

  • [Feature #15865] in expression (mame)

  • Matz: positive.

  • [Feature #15281] Speed up Set#intersect with size check. (tenderlove)

  • Knu will check.