December 2025 - ruby-core - ml.ruby-lang.org

[ruby-core:124131] [Ruby Feature#8948] Frozen regex
by matz (Yukihiro Matsumoto) 11 Dec '25

11 Dec '25

Issue #8948 has been updated by matz (Yukihiro Matsumoto). We found some gems inherited from Regexp and used instance variables on instances, so they would be broken if all Regexp objects become frozen. I think it's unacceptable for Ruby 4.0. Frankly, I don't think freezing the Regexp objects is worth the effort/trouble. Matz. ---------------------------------------- Feature #8948: Frozen regex https://bugs.ruby-lang.org/issues/8948#change-115583 * Author: sawa (Tsuyoshi Sawada) * Status: Assigned * Assignee: Eregon (Benoit Daloze) ---------------------------------------- =begin I see that frozen string was accepted for Ruby 2.1, and frozen array and hash are proposed in https://bugs.ruby-lang.org/issues/8909. I feel there is even more use case for a frozen regex, i.e., a regex literal that generates a regex only once. It is frequent to have a regex within a frequently repeated portion of code, and generating the same regex each time is a waste of resource. At the moment, we can have a code like: class Foo RE1 = /pattern1/ RE2 = /pattern1/ RE3 = /pattern1/ def classify case self when RE1 then 1 when RE2 then 2 when RE3 then 3 else 4 end end end but suppose we have a frozen `Regexp` literal `//f`. Then we can write like: class Foo def classify case self when /pattern1/f then 1 when /pattern1/f then 2 when /pattern1/f then 3 else 4 end end end =end -- https://bugs.ruby-lang.org/

1 0

[ruby-core:123063] [Ruby Feature#21552] allow String.strip and similar to take a parameter similar to String.delete
by MSP-Greg (Greg L) 11 Dec '25

11 Dec '25

Issue #21552 has been reported by MSP-Greg (Greg L). ---------------------------------------- Feature #21552: allow String.strip and similar to take a parameter similar to String.delete https://bugs.ruby-lang.org/issues/21552 * Author: MSP-Greg (Greg L) * Status: Open ---------------------------------------- Regrading `String.strip` (and `lstrip`, `rstrip`, and `!` versions) Some text data representations differentiate between what one might call vertical and horizontal white space, and the 'strip' methods currently strip both. It would be helpful if they had an optional parameter similar to `String.delete` with a one multi-character selector, so one could do: ```ruby t = str.strip " \t" ``` One can use a regex for this, but this much simpler. -- https://bugs.ruby-lang.org/

7 11

[ruby-core:123883] [Ruby Feature#21704] Expose rb_process_status_new to C extensions
by noteflakes (Sharon Rosner) 11 Dec '25

11 Dec '25

Issue #21704 has been reported by noteflakes (Sharon Rosner). ---------------------------------------- Feature #21704: Expose rb_process_status_new to C extensions https://bugs.ruby-lang.org/issues/21704 * Author: noteflakes (Sharon Rosner) * Status: Open ---------------------------------------- A fiber scheduler implementation with a hook for `#process_wait` needs to return a `Process::Status` object, but currently it is not possible for a C extension to directly create an instance of `Process::Status`. The technique currently used in various fiber scheduler implementations is to use `pidfd_open`, poll for fd readiness, then call `Process::Status.wait`, which creates the instance. On recent Linux kernels (6.7 or newer), `io_uring_prep_waitid` can be used to directly wait for process termination, which provides us with the pid and status of the terminated child process, but there's no way to directly create an instance of `Process::Status`, required for implementing the `#process_wait` hook. Exposing the internal `rb_process_status_new` function would allow such an implementation. Using `io_uring_prep_waitid` would also lead to better compatibility of fiber schedulers with calls to `Process.wait(0)` or `Process.wait(-1)`, as those cannot be done using `pidfd_open`. The associated PR is here: https://github.com/ruby/ruby/pull/15213 An working fiber scheduler implementation of `process_wait` using `io_uring_prep_waitid` has been submitted here: https://github.com/socketry/io-event/pull/154 -- https://bugs.ruby-lang.org/

2 1

[ruby-core:124117] [Ruby Bug#15479] Array#reject! modifies literal Array
by sapry1586＠gmail.com (mohamed sapry) 10 Dec '25

10 Dec '25

Issue #15479 has been updated by sapry1586(a)gmail.com (mohamed sapry). Yas ---------------------------------------- Bug #15479: Array#reject! modifies literal Array https://bugs.ruby-lang.org/issues/15479#change-115568 * Author: Eregon (Benoit Daloze) * Status: Closed * Assignee: tenderlovemaking (Aaron Patterson) * ruby -v: ruby 2.6.0p0 (2018-12-25 revision 66547) [x86_64-linux] * Backport: 2.4: DONE, 2.5: DONE, 2.6: DONE ---------------------------------------- This was found by running ruby/spec with -R2 (such as mspec -R2 -fs core/array/reject_spec.rb). TravisCI log on https://travis-ci.org/ruby/spec/jobs/473175799#L539 Here is a simple reproducer. MRI seems to modify the Array literal permanently: ```ruby 3.times do a = [1, 2, 3, 4] puts "initial: #{a}" begin a.reject! do |x| case x when 2 then true when 3 then raise StandardError, 'Oops' else false end end rescue StandardError end puts "after: #{a}" end ``` prints ``` initial: [1, 2, 3, 4] after: [1, 3, 4] initial: [1, 3, 4, 4] after: [1, 3, 4, 4] initial: [1, 3, 4, 4] after: [1, 3, 4, 4] ``` 2.5.3 behaves fine, but trunk is also affected. -- https://bugs.ruby-lang.org/

1 0

[ruby-core:124103] [Ruby Bug#21771] pg-1.6.2 testsuite segfaults in ruby4.0.0dev
by mtasaka (Mamoru TASAKA) 10 Dec '25

10 Dec '25

Issue #21771 has been reported by mtasaka (Mamoru TASAKA). ---------------------------------------- Bug #21771: pg-1.6.2 testsuite segfaults in ruby4.0.0dev https://bugs.ruby-lang.org/issues/21771 * Author: mtasaka (Mamoru TASAKA) * Status: Open * ruby -v: ruby 4.0.0dev (2025-12-09 master edca81a1bb) +PRISM [x86_64-linux] * Backport: 3.2: UNKNOWN, 3.3: UNKNOWN, 3.4: UNKNOWN ---------------------------------------- Looks like pg-1.6.2 https://github.com/ged/ruby-pg/tree/c75ed8da19c356b52d83da2627295760780d3d36 testsuite began to segfault, especially the following ``` #!/bin/bash export PGPORT=54321 export RUBY_PG_TEST_DIR=/builddir/build/BUILD/tmp export RUBYLIB=/builddir/build/BUILD/rubygem-pg-1.6.2-build/pg-1.6.2/usr/share/gems/gems/pg-1.6.2/lib:/builddir/build/BUILD/rubygem-pg-1.6.2-build/pg-1.6.2/usr/lib64/gems/ruby/pg-1.6.2 # The above path should be replaced properly rm -rf $RUBY_PG_TEST_DIR exec ruby -S --verbose \ -r ./spec/helpers \ rspec -f d \ spec/pg/connection_spec.rb -E '' \ --seed 1 ``` segfaults like below (will write later) It seems that segfaults began to happen between commit:706d80830b9f0a5a2eac66251d1417abb2ff143c (no problem) and commit:d7e55f84f2bd62d302b29513d4c4dc8ae9aef96f (segfaults) Tried with commit:edca81a1bb72a9dc54a37766d2c80790dec13884 it still segfaults. Note that ruby-pg *compiled* with commit:706d80830b9f0a5a2eac66251d1417abb2ff143 does *not* segfault with ruby commit:edca81a1bb72a9dc54a37766d2c80790dec13884 , so I suspect that there is something wrong with "inlined" function or so. -- https://bugs.ruby-lang.org/

3 8

[ruby-core:124071] [Ruby Misc#21770] Stop bumping RUBY_PATCHLEVEL in released versions
by k0kubun (Takashi Kokubun) 09 Dec '25

09 Dec '25

Issue #21770 has been reported by k0kubun (Takashi Kokubun). ---------------------------------------- Misc #21770: Stop bumping RUBY_PATCHLEVEL in released versions https://bugs.ruby-lang.org/issues/21770 * Author: k0kubun (Takashi Kokubun) * Status: Open ---------------------------------------- ## Proposal * Stop bumping `RUBY_PATCHLEVEL` from `0` in Ruby 4.0.0+ ## Motivation * As a stable branch maintainer, I find it frustrating that reverting a commit made by `tool/merger.rb` often causes a conflict on `#define RUBY_PATCHLEVEL`. ## Background * From Ruby 2.1.0, we stopped doing multiple patch-level releases for a single version, e.g. [2.0.0-p647](https://www.ruby-lang.org/en/news/2015/08/18/ruby-2-0-0-p647-re… and [2.0.0-p648](https://www.ruby-lang.org/en/news/2015/12/16/ruby-2-0-0-p648-re… for Ruby 2.0.0. * From Ruby 3.2.0, we stopped showing patch levels on `RUBY_DESCRIPTION` [Feature #18513]. We thought "patch levels no longer serves us very well". * Today, we also backport patches using pull requests on GitHub. We often don't bump `RUBY_PATCHLEVEL` there because it's easier to use `git cherry-pick` instead of `tool/merger.rb`. -- https://bugs.ruby-lang.org/

3 2

[ruby-core:123951] [Ruby Bug#21719] Thread deadlock with explicit require of a base clase in Linux Ruby 3.4
by jcuello＠fu.do (Juan Manuel Cuello) 09 Dec '25

09 Dec '25

Issue #21719 has been reported by jcuello(a)fu.do (Juan Manuel Cuello). ---------------------------------------- Bug #21719: Thread deadlock with explicit require of a base clase in Linux Ruby 3.4 https://bugs.ruby-lang.org/issues/21719 * Author: jcuello(a)fu.do (Juan Manuel Cuello) * Status: Open * ruby -v: ruby 3.4.7 (2025-10-08 revision 7a5688e2a2) +PRISM [x86_64-linux] * Backport: 3.2: UNKNOWN, 3.3: UNKNOWN, 3.4: UNKNOWN ---------------------------------------- I originally [reported the issue](https://github.com/fxn/zeitwerk/issues/321) in Zeitwerk, but we then figured out that it seems to be related to Ruby. Basically, I'm having a threads deadlock when using requires with autoloadable classes: ```ruby # jobs/base.rb # module Jobs class Base end end # jobs/a.rb # require './jobs/base' module Jobs class A < Base def perform puts self.class.name end end end # jobs/b.rb # module Jobs class B < Base def perform puts self.class.name end end end # start.rb # module Jobs autoload :Base, './jobs/base' autoload :A, './jobs/a' autoload :B, './jobs/b' end a = Thread.new { Jobs::A.new.perform } b = Thread.new { Jobs::B.new.perform } a.join b.join ``` ``` ruby --version && ruby start.rb ruby 3.4.7 (2025-10-08 revision 7a5688e2a2) +PRISM [x86_64-linux] start.rb:12:in 'Thread#join': No live threads left. Deadlock? (fatal) 3 threads, 3 sleeps current:0x00005ca30dfbc500 main thread:0x00005ca30dd30330 * #<Thread:0x000076b1a7d6a658 sleep_forever> rb_thread_t:0x00005ca30dd30330 native:0x000076b1a81b87c0 int:0 * #<Thread:0x000076b1a7d2e928 start.rb:9 sleep_forever> rb_thread_t:0x00005ca30dfbc500 native:0x000076b18c74d6c0 int:0 depended by: tb_thread_id:0x00005ca30dd30330 * #<Thread:0x000076b1a7d2e3b0 start.rb:10 sleep_forever> rb_thread_t:0x00005ca30dfb0fd0 native:0x000076b18c54b6c0 int:0 mutex:0x00005ca30dfe2b60 cond:1 from start.rb:12:in '<main>' ``` Note the require './jobs/base' in `jobs/a.rb`. If I remove it, everything works. The same happens if I add the same explicit require in `jobs/b.rb`. It seems to have been fixed in ruby 3.4 in commit:ea2af5782df63266577ba08a4ef4c30b6d63e564, but not apparent in Linux (which is my case) until commit:6fbc32b5d0da31535cccc0eca1853273313a0b52 I'm not familiar with the ruby codebase, so It's not clear to me why the change to prism fixed the threads issue and why it didn't have impact in Linux until the other fix, but bisecting the source code and running each revision against the code above, that is what I came to. I can create a PR to backport the Linux fix to `ruby_3_4` branch, as in `master` everything is working as expected. -- https://bugs.ruby-lang.org/

2 1

[ruby-core:122240] [Ruby Bug#21363] `Namespace.current` should always return the Namespace in which it was defined
by tenderlovemaking (Aaron Patterson) 09 Dec '25

09 Dec '25

Issue #21363 has been reported by tenderlovemaking (Aaron Patterson). ---------------------------------------- Bug #21363: `Namespace.current` should always return the Namespace in which it was defined https://bugs.ruby-lang.org/issues/21363 * Author: tenderlovemaking (Aaron Patterson) * Status: Open * ruby -v: ruby 3.5.0dev (2025-05-22T23:07:21Z rm-assertion 17e71c7a24) +PRISM [arm64-darwin24] * Backport: 3.2: UNKNOWN, 3.3: UNKNOWN, 3.4: UNKNOWN ---------------------------------------- I think `Namespace.current` should always return the namespace in which it was defined. Here is an example to demonstrate what I mean: ```ruby File.binwrite("ns.rb", <<-RUBY) # namespace 3 module M def self.test p Namespace.current end TEST = -> { p Namespace.current } end RUBY ns = Namespace.new ns.load "./ns.rb" p Namespace.current ns::M.test ns::M::TEST.call ``` I expect the output of `ns::M.test` and `ns::M::TEST.call` to be the same. Instead the output is like this: ``` #<Namespace:2,user,main> #<Namespace:3,user,optional> #<Namespace:2,user,main> ``` I think a method and lambda defined in the same namespace should return the same value for `Namespace.current` -- https://bugs.ruby-lang.org/

2 3

[ruby-core:122114] [Ruby Bug#21341] `Namespace is not a module (TypeError)` without enabling the namespace
by yahonda (Yasuo Honda) 09 Dec '25

09 Dec '25

Issue #21341 has been reported by yahonda (Yasuo Honda). ---------------------------------------- Bug #21341: `Namespace is not a module (TypeError)` without enabling the namespace https://bugs.ruby-lang.org/issues/21341 * Author: yahonda (Yasuo Honda) * Status: Open * ruby -v: ruby 3.5.0dev (2025-05-15T08:25:56Z master 427ede2dde) +PRISM [x86_64-linux] * Backport: 3.2: UNKNOWN, 3.3: UNKNOWN, 3.4: UNKNOWN ---------------------------------------- Ruby on Rails test case has the `module Namespace`. https://github.com/rails/rails/blob/main/activemodel/test/validators/namesp… ```ruby module Namespace class EmailValidator < ::EmailValidator end end ``` This code fails against Ruby 3.5.0dev without enabling the namespace feature. ### Steps to reproduce ```ruby $ ruby -ve 'module Namespace; end' ``` ### Expected behavior It should run without errors. ### Actual behavior It raises the TypeError. ```ruby $ ruby -ve 'module Namespace; end' ruby 3.5.0dev (2025-05-15T08:25:56Z master 427ede2dde) +PRISM [x86_64-linux] -e:1:in '<main>': Namespace is not a module (TypeError) ruby:0: previous definition of Namespace was here ``` Raising this TypeError with RUBY_NAMESPACE=1 looks expected to me. ```ruby $ RUBY_NAMESPACE=1 ruby -ve 'module Namespace; end' ruby 3.5.0dev (2025-05-15T08:25:56Z master 427ede2dde) +PRISM [x86_64-linux] ruby: warning: Namespace is experimental, and the behavior may change in the future! See doc/namespace.md for known issues, etc. -e:1:in '<main>': Namespace is not a module (TypeError) ruby:0: previous definition of Namespace was here ``` -- https://bugs.ruby-lang.org/

5 8

[ruby-core:121955] [Ruby Bug#21320] Namespaces leak with constant lookup
by fxn (Xavier Noria) 09 Dec '25

09 Dec '25

Issue #21320 has been reported by fxn (Xavier Noria). ---------------------------------------- Bug #21320: Namespaces leak with constant lookup https://bugs.ruby-lang.org/issues/21320 * Author: fxn (Xavier Noria) * Status: Open * Backport: 3.2: UNKNOWN, 3.3: UNKNOWN, 3.4: UNKNOWN ---------------------------------------- The following program ```ruby X = :top class C X = :super end class D < C p X end ``` prints `:super` normally, and `:top` if running under a namespace. -- https://bugs.ruby-lang.org/

3 4