Misc #16232: DevelopersMeeting20191017Japan

• Status: Closed
• Assignee: -

[mame (Yusuke Endoh)]

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: 10/17 13:00-17:00
Place and Sign-up: (See the Log)
log: https://docs.google.com/document/d/1-IC98nOPY_FZnne2PXILYAaxt6PqHfhphAI908K3vD8

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.

[mame (Yusuke Endoh)]

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

[mame (Yusuke Endoh)]

• Description updated (diff)

[byroot (Jean Boussier)]

• [Feature #16029] Expose fstring related APIs to C-extensions (byroot)
  • Apparently the current implementation is complicated to expose, but no details were provided.
  • Is there something I or others could change to the implementation so that it could be exposed?
• [Feature #16038] Provide a public WeakMap that compares by equality rather than by identity (byroot)
  • Matz asked for real world use-case, which I did provide.
  • In short it's useful for implementing value objects deduplication, just like how the fstring table works, but for user defined, more complex types.

[jeremyevans0 (Jeremy Evans)]

• [Bug #10314] Default argument lookup fails in Ruby 2.2 for circular shadowed variable names (jeremyevans)
  • Do we want to change def foo(bar=bar) from warning to SyntaxError using the patch?
• [Bug #11055] autoload resets private_constant (jeremyevans)
  • Do we want to copy constant visibility information across the autoload using the patch?
• [Bug #15267] File.basename + File.extname does not restore the original name (jeremyevans)
  • Do we want to make them restore the original name using the patch?

[sam.saffron (Sam Saffron)]

[Feature #16245] Add interfaces to count and measure size all IMEMO objects (Sam Saffron)

• Would love to see this included in 2.7, refined proposal does not add any new APIs.

[rafaelfranca (Rafael França)]

• [Feature #13683] Add strict Enumerable#single
  • Matz didn't like the single name but we have a proposal for #only

[kou (Kouhei Sutou)]

• [Bug #16143] BOM UTF-8 is not removed after rewind (kou)
  • Can we commit this? I've reviewed. I think that this is ready to merge.

[zverok (Victor Shepelev)]

• [Feature #15822] Add Hash#except
  • The method is really useful, even with ActiveSupport-less codebases I constantly tend to redefine it with core ext or refinements. Hash#slice was merged in 2.5; it was initially discussed in #8499 alongside the except, but from the discussion, it is not obvious why #except was "lost" :(

[jeremyevans0 (Jeremy Evans)]

• [Feature #16131] Remove $SAFE, taint and trust (jeremyevans)
  • Does anyone have time to review the patch (extensive changes, mostly code deletion)?
  • How do we want to handle included libraries with separate upstreams that want to be compatible with older Ruby versions (bundler, rubygems, etc.)?

[ko1 (Koichi Sasada)]

• [Feature #16255] Make monitor.rb built-in (ko1)
  • maybe there is no problem.
  • Should we make MonitorMixin built-in?
• [Feature #16254] MRI internal: Define built-in classes in Ruby with __intrinsic__ syntax (ko1)
  • only on small start, maybe there is no problem.
  • many points we need to decide.

[mame (Yusuke Endoh)]

• [Feature #16253] Shorthand "forward everything" syntax (mame)
  • How about introducing def foo(...); bar(...); end? It does not solve the compatibility issue of keyword argument separation, but it would provide a useful shorthand for delegation if the code doesn't have to work on 2.6.

[mame (Yusuke Endoh)]

• [Feature #16150] Add a way to request a frozen string from to_s
  • Symbol#to_s now returns a frozen string, and this brought at least seven incompatibility issues. To make sure: is it okay to introduce this change in 2.7.0-preview2?

[Dan0042 (Daniel DeLorme)]

• [Feature #16120] Omitted block argument if block starts with dot-method call (Dan0042)
  • last time Matz said "Give me time to consider it"; there is now a patch ready; is it ok to accept?

[znz (Kazuhiro NISHIYAMA)]

• [Feature #13083] {String|Symbol}#match{?} with nil returns falsy as Regexp#match{?}
  • Matz said "Those methods (but =~) should consistently raise exceptions." and pull request's conflicts resolved again.

[alanwu (Alan Wu)]

• [Misc #16258] Combine call info and cache to speed up method invocation
  • Looking for feedback and reviews. I think this offers a good perf boost.
• [Bug #15912] Allow some reentrancy during TracePoint events
  • I have seen quite a few people confused about Byebug's REPL not working as they would expect due to this issue. I think it's important to come up with some solution for this in two seven.

[osyo (manga osyo)]

• [Feature #16142] Implement code_range in Proc and Method - Ruby master - Ruby Issue Tracking System
  • Propose an API to get code position of Proc and Method so that we can get body of them (especially of a Proc).
  • I want to discuss method names and return values

[mame (Yusuke Endoh)]

• Status changed from Open to Closed