Misc #20574: DevMeeting-2024-07-11

• Status: Open
• Assignee: -

[mame (Yusuke Endoh)]

The next dev meeting

Date: 2024/07/11 13:00-17:00 (JST)
Log: TBD

• 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 record of the discussion in the 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 of the meeting 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.

• It is recommended to add a comment by 2024/07/08. We hold a preparatory meeting to create an agenda a few days before the dev-meeting.
• The format is strict. We'll use this script to automatically create an markdown-style agenda. 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. We appreciate it if you could write a short summary and update from a previous discussion.

[mame (Yusuke Endoh)]

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

[tompng (tomoya ishida)]

• [Bug #20433] Hash.inspect for some hash returns syntax invalid representation
  • Change Hash#inspect style to {key: value} or not

[shugo (Shugo Maeda)]

• [Feature #20576] Add MatchData#bytebegin and MatchData#byteend
  • Matz doesn't like the names bytebegin and byteend.
    • Other names: byte_begin/byte_end, begin_in_bytes/end_in_bytes
    • If byte_begin/byte_end are chosen, should we add aliases for existing methods such as byteslice?
    • Since these methods are for advanced users, it may be more important to prioritize consistency with existing methods over readability.

[byroot (Jean Boussier)]

• [Bug #20593] Kernel#format emits a too many arguments for format string warning when called with a single hash and no key is used
  • format emits warnings when too many positional arguments were passed, but doesn't do so if too many hash keys were passed.
  • This makes sense to me because extra named argument are generally not indicative of a bug.
  • However if no key is consumed at all, it does emit a warning: format("test", unused: 2) # warning: too many arguments for format string
  • I think it's a bug and no warning should be emitted.

[ufuk (Ufuk Kayserilioglu)]

• [Feature #19979] Allow methods to declare that they don't accept a block via &nil
  • Based on the discussion in DevMeeting at RubyKaigi 2024, it seems this feature is still considered valuable.
  • I've rebased @nobu (Nobuyoshi Nakada) 's original work and built upon it to create a PR: https://github.com/ruby/ruby/pull/11065
  • The PR adds support for the new syntax for both parsers and both compilers (parse.y and prism)
  • Do we still want to go ahead with this feature?