Issue #22249 has been updated by byroot (Jean Boussier). * [Feature #22232] Deprecate `RHASH_TBL` and associated APIs (byroot) * I would like to deprecate `RHASH_TBL`, `RHASH_TBL_RAW` and `rb_hash_bulk_insert_into_st_table`. * It's a dangerous API because it allow bypassing write barriers * It restrict evolution of `RHash`, as we must always be able to convert a Hash into a public `st_table`. * gem-codesearch only revealed very old and low download gems. * All codesearch results have an equivalent `rb_hash_*` API, proving `RHASH_TBL` is useless. * [Feature #22236] New API for adjustable JIT warmup (byroot) * JIT warmup can be a challenge in production. * After a deploy JIT warmup can cause high latency, so it may need to be tuned to avoid timeouts, queuing, etc. * Current tuning parameters like `--yjit-call-threshold` are hard to reason about, imprecise and need frequent update as the application changes. * I'd like YJIT, and potentially ZJIT to have an adjustable `max_compile_time_ns`. * When `RubyVM::YJIT.runtime_stats[:compile_time_ns]` goes over `max_compile_time_ns` stop compiling. * When `max_compile_time_ns` is assigned to a value higher than current `compile_time_ns` re-enable compilation. * It only need to be best effort. * See ticket for example usage. ---------------------------------------- Misc #22249: DevMeeting-2026-09-10 https://bugs.ruby-lang.org/issues/22249#change-118578 * Author: mame (Yusuke Endoh) * Status: Open ---------------------------------------- # The next dev meeting **Date: 2026/09/10 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 2026/09/07. 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](https://gist.github.com/mame/b0390509ce1491b43610b9ebb665eb86). 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. -- https://bugs.ruby-lang.org/

Issue #22249 has been updated by himura467 (Akito Shitara). * [Feature #22056] Zero-Copy String Constructor Backed by Arbitrary Ruby Object (himura467) * A C API creating a String that references memory owned by another Ruby object. * It was blocked on the `RSTRING_PTR()` NUL-termination invariant (https://bugs.ruby-lang.org/issues/22056#note-19); https://bugs.ruby-lang.org/issues/22056#note-20 proposes that only new opt-in APIs produce Strings that are not NUL-terminated. * Would like to ask whether this direction is acceptable, and whether the C API can proceed on it. ---------------------------------------- Misc #22249: DevMeeting-2026-09-10 https://bugs.ruby-lang.org/issues/22249#change-118627 * Author: mame (Yusuke Endoh) * Status: Open ---------------------------------------- # The next dev meeting **Date: 2026/09/10 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 2026/09/07. 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](https://gist.github.com/mame/b0390509ce1491b43610b9ebb665eb86). 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. -- https://bugs.ruby-lang.org/

Issue #22249 has been updated by tekknolagi (Maxwell Bernstein). * [https://bugs.ruby-lang.org/issues/22272] Propose Kevin Menard (@nirvdrum) as a core committer (tekknolagi) * I am proposing we make Kevin Menard, a long-time and frequent contributor, a committer. * This will also help ZJIT: it would be nice if he could merge PRs. ---------------------------------------- Misc #22249: DevMeeting-2026-09-10 https://bugs.ruby-lang.org/issues/22249#change-118775 * Author: mame (Yusuke Endoh) * Status: Open ---------------------------------------- # The next dev meeting **Date: 2026/09/10 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 2026/09/07. 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](https://gist.github.com/mame/b0390509ce1491b43610b9ebb665eb86). 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. -- https://bugs.ruby-lang.org/

Issue #22249 has been updated by ufuk (Ufuk Kayserilioglu). * [Feature #22300] `Ractor.check_isolation`: report Ractor isolation violations as warnings instead of raising (ufuk) * The proposal gives the ecosystem two things it does not have today for Ractor-safety: 1. a burn-down list, to make a codebase Ractor-safe; 2. a ratchet, to keep it Ractor-safe. * The attached patch has been used to find and burn-down Ractor-safety violations in the Rails codebase, as well as some internal Shopify codebases. * Can we ship a version of this in Ruby 4.1? ---------------------------------------- Misc #22249: DevMeeting-2026-09-10 https://bugs.ruby-lang.org/issues/22249#change-118823 * Author: mame (Yusuke Endoh) * Status: Open ---------------------------------------- # The next dev meeting **Date: 2026/09/10 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 2026/09/07. 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](https://gist.github.com/mame/b0390509ce1491b43610b9ebb665eb86). 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. -- https://bugs.ruby-lang.org/

Issue #22249 has been updated by nobu (Nobuyoshi Nakada). * [Feature #22134] Faster rb_scan_args() for keyword args (optimization) (nobu) * Luke proposes `:^` to avoid keyword hash duplication and `rb_get_kwargs_const` for non-destructive lookup. * I suggest `RB_SCAN_ARGS_BORROW_KEYWORDS` (`"^"`) as both a format fragment and a feature detection macro. * I also suggest `rb_lookup_kwargs` / `rb_extract_kwargs`, retaining `rb_get_kwargs` as a compatibility alias; my prototype showed 1.13–1.35x speedups in successful keyword-parsing microbenchmarks. ---------------------------------------- Misc #22249: DevMeeting-2026-09-10 https://bugs.ruby-lang.org/issues/22249#change-118844 * Author: mame (Yusuke Endoh) * Status: Open ---------------------------------------- # The next dev meeting **Date: 2026/09/10 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 2026/09/07. 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](https://gist.github.com/mame/b0390509ce1491b43610b9ebb665eb86). 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. -- https://bugs.ruby-lang.org/