Project

General

Profile

Actions

Misc #20949

closed

DevMeeting-2025-01-09

Added by mame (Yusuke Endoh) about 1 month ago. Updated 9 days ago.

Status:
Closed
Assignee:
-
[ruby-core:120215]

Description

The next dev meeting

Date: 2025/01/09 13:00-17:00 (JST)
Log: https://github.com/ruby/dev-meeting-log/tree/master/2025

  • 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 2025/01/06. 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.

Related issues 1 (1 open0 closed)

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

Updated by mame (Yusuke Endoh) about 1 month ago

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

Updated by byroot (Jean Boussier) 13 days ago

  • [Feature #20993] Allow class <constant-path> = <expression> syntax (byroot)
    • Useful for defining Struct and Data subclasses. See [Bug #20943]
    • It's just sugar for <constant-path> = <expression>; class <constant-path>
    • Would be allowed for module as well.
  • [Feature #20878] A new C API to create a String by adopting a pointer (byroot)
    • Following the last discussion I think the API could receive a pointer to the free function to use.
    • e.g. str = rb_enc_str_adopt(buf->ptr, buf->len, buf->capa, rb_utf8_encoding(), free);
    • This allow the API to fallback to a copy if the free function isn't compatible with ruby_xfree

Updated by Eregon (Benoit Daloze) 12 days ago

  • [Feature #21005] Update the source location method to include line start/stop and column start/stop details (eregon)
    • How about adding end line and start/end columns to #source_location? It seems straightforward and compatible.
    • How about a new #code_location method returning an object with line/column/offset info and also a convenient method to return the source code snippet of that location? See https://bugs.ruby-lang.org/issues/21005#note-3

Updated by sampersand2 (Sam Westerman) 10 days ago

  • [Feature #21015] Add in a -g flag, like -s but with a few more quality of life features (sampersand2)
    • There's a hole in ruby for very simple argument processing to very short scripts (<=10 lines.)
    • The -s flag somewhat fills this, but most egregiously doesn't let you chain shortform options (-abc != -a -b -c).
    • I've gotten positive sentiment from quite a few people on the Ruby discord about this, so I think it's worth discussing
Actions #5

Updated by mame (Yusuke Endoh) 9 days ago

  • Description updated (diff)
  • Status changed from Open to Closed
Actions

Also available in: Atom PDF

Like0
Like0Like0Like0Like0Like0