Misc #21019: DevMeeting-2025-02-13

• Status: Closed
• Assignee: -

[mame (Yusuke Endoh)]

The next dev meeting

Date: 2025/02/13 13:00-17:00 (JST)
Log: https://github.com/ruby/dev-meeting-log/blob/master/2025/DevMeeting-2025-02-13.md

• 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/02/10. 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

[Eregon (Benoit Daloze)]

• [Bug #20998] rb_str_locktmp() changes flags of frozen strings and string literals (eregon)
  • Current behavior on frozen strings is buggy (should not mutate the flags of possibly-shared frozen strings).
  • What should be the behavior for rb_str_locktmp() on frozen strings? No-op or raise error (e.g. FrozenError)?

[peterzhu2118 (Peter Zhu)]

• [Feature #21084] Declare objects have weak references (peterzhu2118)
  • The current way of marking weak references uses rb_gc_mark_weak(VALUE *ptr).
  • This presents challenges because Ruby's GC is incremental, meaning that if the ptr changes (e.g. realloc'd or free'd), then we could have an invalid memory access.
  • This also overwrites *ptr = Qundef if *ptr is dead, which prevents any cleanup to be run (e.g. freeing memory or deleting entries from hash tables).
  • This ticket proposes rb_gc_declare_weak_references which declares that an object has weak references and calls a cleanup function after marking, allowing the object to clean up any memory for dead objects.

[k0kubun (Takashi Kokubun)]

• [Feature #21116] Extract RJIT as a third-party gem (k0kubun)
  • Are we okay with removing RJIT (--rjit) from the Ruby core?

[byroot (Jean Boussier)]

• [Bug #21102] Unexpected encoding when concatenating ASCII string with ASCII compatible string (toy)
  • Should ascii_string + utf8_string return an ASCII or UTF-8 string when both have 7bit coderange?

[mame (Yusuke Endoh)]

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