Project

General

Profile

Misc #16262

DevelopersMeeting20191128Japan

Added by mame (Yusuke Endoh) 30 days ago. Updated 3 days ago.

Status:
Open
Priority:
Normal
Assignee:
-
[ruby-core:95420]

Description

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/11/28 13:00-17:00
Place, Sign-up, and Log: https://docs.google.com/document/d/1AZ74HXEedKksJwhEUPIlnRxAUgchndZPZYAKjGPMsFI/edit#

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.


Related issues

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

History

#1

Updated by mame (Yusuke Endoh) 30 days ago

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

Updated by mame (Yusuke Endoh) 30 days ago

  • Description updated (diff)

Carry over:

  • [Bug #15912] Allow some reentrancy during TracePoint events (alanwu)

    • 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.
  • [Feature #16142] Implement code_range in Proc and Method - Ruby master - Ruby Issue Tracking System (osyo)

    • 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

Updated by jeremyevans0 (Jeremy Evans) 30 days ago

  • [Feature #16129] Call initialize_clone with freeze: false if clone called with freeze: false (jeremyevans0)
    • Without this, use of clone(freeze: false) on objects not expecting it leads to unexpected state.
    • Allows fixing problems in delegate and set.
  • [Bug #16242] Refinements method call to failed (jeremyevans0)
    • OK to fix modules that are refined and prepended by creating an iclass for the module (and not just the module's origin)?
  • [Bug #13446] refinements with prepend for module has strange behavior (jeremyevans0)
    • OK to fix case where prepend is used on a refined module after the module is included by creating an origin iclass during inclusion?

Updated by duerst (Martin Dürst) 25 days ago

  • [Feature #16262] Enumerable#each_tuple, and [Feature #4539] Array#zip_with
    • zip_with really comes in handy on occasion, and is available in many programming languages, in particular functional programming languages.

Updated by zverok (Victor Shepelev) 22 days ago

(Sorry for being over-active. On the bright side, it could be a final bunch from me)

Carry-over from tickets with feedback:

  • [Feature #16122] Struct::Value: simple immutable value object. First version of the proposal was not clear enough, I am sorry for it. Clarified the descrition, added links and answered some possible questions.
  • [Feature #15822] Add Hash#except. Matz: "We didn't see the need for Hash#except yet. Any (real world use-case)? I don't think the name except is the best name for the behavior." Added real-life examples and name justifications.

This two proposals would make sense only if .: would not be reverted (which, to the best of my understaning, is now doubtful)

  • [Feature #16261] Enumerable#each_splat and Enumerator#splat allowing to mitigate 1-element/multi-element enumerators
  • [Feature #16264] Real "callable instance method" object. .:method to be a first-class thing, instead of Symbol#to_proc trick

Updated by jonathanhefner (Jonathan Hefner) 12 days ago

  • [Feature #15323] Enumerable#filter_map
    • This feature has already been merged, but there may have been some confusion regarding the implementation.
    • It currently selects only truthy values, but should it select all non-nil values, like Array#compact? (See https://bugs.ruby-lang.org/issues/15323#note-17)
    • If so, is the name filter_map still a good choice? Or should it be changed to something like compact_map?

Updated by osyo (manga osyo) 12 days ago

  • [Feature #16293] Numbered parameter confirmation in Ruby 2.7
    • Numbered parameter confirmation in Ruby 2.7

Updated by methodmissing (Lourens Naudé) 7 days ago

  • [Misc #16291] Introduce support for resize in rb_ary_freeze and prefer internal use of rb_ary_freeze and rb_str_freeze for String and Array types (lourens)
    • Builds onto the capacity shrinking feature introduced by rb_str_freeze, targeting Array
    • Many internal uses that froze String types did not use the rb_str_freeze variation and could not benefit from resizing capacity on freeze
    • Implemented the same for Array
    • Let Array#freeze call rb_ary_freeze to expose the shrinking capability to user code too (as recommended by Shyouhei) for parity with String#freeze already doing the same

Updated by alanwu (Alan Wu) 3 days ago

  • [Bug #15620] Block argument usage affects lambda semantic
    • I find the current behaviour unreasonably confusing and would like to see improvement, even though the bug doesn't really show up in the real world often.
    • I have a pull request which restores the behaviour found in Ruby 2.4.x and warns about it, based off of matz's comment in [ruby-core:94054].
    • Could someone confirm that is the desired fix? If it is the fix we want, could someone review the PR?

Also available in: Atom PDF