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

[ruby-core:122558] [Ruby Bug#21446] StackOverflow when changing visibility in reopened refinement
by luke-gru (Luke Gruber) 16 Dec '25

16 Dec '25

Issue #21446 has been reported by luke-gru (Luke Gruber). ---------------------------------------- Bug #21446: StackOverflow when changing visibility in reopened refinement https://bugs.ruby-lang.org/issues/21446 * Author: luke-gru (Luke Gruber) * Status: Open * ruby -v: 3.5.0 * Backport: 3.2: UNKNOWN, 3.3: UNKNOWN, 3.4: UNKNOWN ---------------------------------------- ```ruby class A def a :a end end class B < A end module R refine B do private :a end end module R refine B do public :a end end using R B.new.a # StackOverflow ``` I would expect it to change the visibility, not to overflow the stack. -- https://bugs.ruby-lang.org/

4 3

[ruby-core:123576] [Ruby Bug#21654] Set#new calls extra methods compared to previous versions
by tenderlovemaking (Aaron Patterson) 16 Dec '25

16 Dec '25

Issue #21654 has been reported by tenderlovemaking (Aaron Patterson). ---------------------------------------- Bug #21654: Set#new calls extra methods compared to previous versions https://bugs.ruby-lang.org/issues/21654 * Author: tenderlovemaking (Aaron Patterson) * Status: Open * ruby -v: ruby 3.5.0dev (2025-10-24T15:50:47Z master a9f24aaccb) +PRISM [arm64-darwin25] * Backport: 3.2: UNKNOWN, 3.3: UNKNOWN, 3.4: UNKNOWN ---------------------------------------- I'm trying to test Ruby 3.5.0 with our Rails application and we've found that `Set.new` is now causing extra database queries to happen. The changes in d4020dd5faf call "size" on enumerable objects that are passed to the `new` method, and this causes extra "COUNT" queries to happen with ActiveRecord associations. For example: ```ruby Set.new(some_activerecord_association) ``` Previously, the above code would only do one query by iterating over the association. Now it issues two queries, a count query, and then the normal query for results. Since d4020dd5faf is dealing with endless ranges, I would like to narrow the scope from all Enumerable objects to just Ranges. Unfortunately, I noticed we have a test like this: ```ruby assert_raise(ArgumentError) { Set.new(1.upto(Float::INFINITY)) } ``` I'm not sure how we can handle such a case without testing `size`. -- https://bugs.ruby-lang.org/

8 19

[ruby-core:124240] [Ruby Feature#6012] Proc#source_location also return the column
by Eregon (Benoit Daloze) 16 Dec '25

16 Dec '25

Issue #6012 has been updated by Eregon (Benoit Daloze). Right, I thought about that too but forgot to write it. Several gems have already adapted to this feature and their functionality and/or tests might rely on having the extra information, so it's definitely not great to remove this last minute. If https://github.com/ruby/prism/pull/3808 had been merged already we'd make the entire method unusable in Prism, which certainly sounds bad. I think we should do https://github.com/ruby/ruby/pull/15580 ---------------------------------------- Feature #6012: Proc#source_location also return the column https://bugs.ruby-lang.org/issues/6012#change-115726 * Author: rogerdpack (Roger Pack) * Status: Open * Assignee: nobu (Nobuyoshi Nakada) ---------------------------------------- As originally suggested in http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-core/42418 Suggestion/feature request: have #source_location also return the beginning column where it was defined. ["test.rb", 8, 33] Thanks! -roger- -- https://bugs.ruby-lang.org/

1 0

[ruby-core:124235] [Ruby Feature#6012] Proc#source_location also return the column
by vo.x (Vit Ondruch) 16 Dec '25

16 Dec '25

Issue #6012 has been updated by vo.x (Vit Ondruch). And RSpec were also adjusted to the new behavior AFAICT: https://github.com/rspec/rspec/pull/282/commits/1c20fa80772ca7a1ed0512056ce… ---------------------------------------- Feature #6012: Proc#source_location also return the column https://bugs.ruby-lang.org/issues/6012#change-115721 * Author: rogerdpack (Roger Pack) * Status: Open * Assignee: nobu (Nobuyoshi Nakada) ---------------------------------------- As originally suggested in http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-core/42418 Suggestion/feature request: have #source_location also return the beginning column where it was defined. ["test.rb", 8, 33] Thanks! -roger- -- https://bugs.ruby-lang.org/

1 0

[ruby-core:124234] [Ruby Feature#6012] Proc#source_location also return the column
by vo.x (Vit Ondruch) 16 Dec '25

16 Dec '25

Issue #6012 has been updated by vo.x (Vit Ondruch). Just FTR, not sure how the revert is supposed to look like, but at least Pry was adjusted for the new behavior: https://github.com/pry/pry/pull/2357 It does not benefit from columns, but I suspect the revert would somehow influenced also the end of method location. ---------------------------------------- Feature #6012: Proc#source_location also return the column https://bugs.ruby-lang.org/issues/6012#change-115720 * Author: rogerdpack (Roger Pack) * Status: Open * Assignee: nobu (Nobuyoshi Nakada) ---------------------------------------- As originally suggested in http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-core/42418 Suggestion/feature request: have #source_location also return the beginning column where it was defined. ["test.rb", 8, 33] Thanks! -roger- -- https://bugs.ruby-lang.org/

1 0

[ruby-core:124232] [Ruby Feature#6012] Proc#source_location also return the column
by Eregon (Benoit Daloze) 16 Dec '25

16 Dec '25

Issue #6012 has been updated by Eregon (Benoit Daloze). mame (Yusuke Endoh) wrote in #note-32: > I record the summary of the discussion regarding Matz's decision to revert this for now. The decision was based on a combination of several reasons: Thank you for documenting that. It feels to me like the decision was taken while we were in the middle of discussing https://bugs.ruby-lang.org/issues/21783, where we seem to now have reached an agreement, but the revert decision (and revert PR merged) was taken without any time for me to even reply there. > * Unclear use cases The fact many issues have been filed about this seems to show this is clearly a wanted feature. It has always been useful to find where a method/block is defined. https://rubygems.org/gems/method_source has 700 millions downloads, what other proof do we need? > * Difficulty in changing `Binding#source_location` (#6012#note-24, #21005#note-19) I wasn't aware of these, but I think this is much less needed than on {Proc,Method,UnboundMethod}. Unless I'm missing something, a Binding doesn't always have a properly-defined source location/definition, e.g. for `b = binding`. It has a start line if we consider that to be at the line of the `binding` call, but not really an end line/column. IOW it's not a "scope" unlike a method or block, and seems much less useful. > * Related issues: > * We may need to adjust Proc#source_location's position (#21784). > * We need to discuss column units (bytes vs characters) (#21783). I'm fixing both of these in https://github.com/ruby/ruby/pull/15580. Both issues seem to have rather clear agreements at this point. > * Timing: We can still revert without compatibility issues at this point. The feature has been implemented since 9th January, almost a year ago. It's not been in a proper release yet of course but it has been in multiple previews. I'm not sure if other people have tried it already, but I'm pretty confident a bunch of people are gonna be disappointed if this is removed last minute and it needs another year before it's in a Ruby release. Do we really want to encourage heuristics like https://bugs.ruby-lang.org/issues/20999#note-1 vs a proper a solution by providing the necessary information in `{Method,UnboundMethod,Proc}#source_location`? ---------------------------------------- Feature #6012: Proc#source_location also return the column https://bugs.ruby-lang.org/issues/6012#change-115718 * Author: rogerdpack (Roger Pack) * Status: Open * Assignee: nobu (Nobuyoshi Nakada) ---------------------------------------- As originally suggested in http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-core/42418 Suggestion/feature request: have #source_location also return the beginning column where it was defined. ["test.rb", 8, 33] Thanks! -roger- -- https://bugs.ruby-lang.org/

1 0

[ruby-core:124229] [Ruby Feature#6012] Proc#source_location also return the column
by mame (Yusuke Endoh) 16 Dec '25

16 Dec '25

Issue #6012 has been updated by mame (Yusuke Endoh). Status changed from Closed to Open I record the summary of the discussion regarding Matz's decision to revert this for now. The decision was based on a combination of several reasons: * Unclear use cases * The description of #6012 lacked a use case. * The use case presented in #21005 was not convincing. * Difficulty in changing `Binding#source_location` (#6012#note-24, #21005#note-19) * `Binding#source_location` still returns `[file, lineno]`. * Implementation issues: It was challenging to preserve the location information of `Kernel#binding` calls within the ISeq. * Compatibility issues: `eval(code, nil, *binding.source_location)` is used in several gems; adding column information would break them. * Related issues: * We may need to adjust Proc#source_location's position (#21784). * We need to discuss column units (bytes vs characters) (#21783). * Timing: We can still revert without compatibility issues at this point. ---------------------------------------- Feature #6012: Proc#source_location also return the column https://bugs.ruby-lang.org/issues/6012#change-115715 * Author: rogerdpack (Roger Pack) * Status: Open * Assignee: nobu (Nobuyoshi Nakada) ---------------------------------------- As originally suggested in http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-core/42418 Suggestion/feature request: have #source_location also return the beginning column where it was defined. ["test.rb", 8, 33] Thanks! -roger- -- https://bugs.ruby-lang.org/

1 0

[ruby-core:124220] [Ruby Feature#6012] Proc#source_location also return the column
by matz (Yukihiro Matsumoto) 16 Dec '25

16 Dec '25

Issue #6012 has been updated by matz (Yukihiro Matsumoto). Although last minute, we will cancel this feature in 4.0 because of design ambiguities such as whether to return column positions in bytes or characters as in #21783. Matz. ---------------------------------------- Feature #6012: Proc#source_location also return the column https://bugs.ruby-lang.org/issues/6012#change-115703 * Author: rogerdpack (Roger Pack) * Status: Closed * Assignee: nobu (Nobuyoshi Nakada) ---------------------------------------- As originally suggested in http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-core/42418 Suggestion/feature request: have #source_location also return the beginning column where it was defined. ["test.rb", 8, 33] Thanks! -roger- -- https://bugs.ruby-lang.org/

1 0

[ruby-core:123754] [Ruby Feature#21678] Enumerable#rfind
by kddnewton (Kevin Newton) 15 Dec '25

15 Dec '25

Issue #21678 has been reported by kddnewton (Kevin Newton). ---------------------------------------- Feature #21678: Enumerable#rfind https://bugs.ruby-lang.org/issues/21678 * Author: kddnewton (Kevin Newton) * Status: Open ---------------------------------------- I'd like to introduce `rfind` to enumerable, which would effectively be the same as `reverse_each.find`. I've found myself using this a surprising number of times, and have been surprised at its omission. That means either falling back to `reverse_each` or `rindex`. For context, here are a couple of examples of this in the wild: * [pry](https://github.com/pry/pry/blob/80816f596774d00afdc81a555724b0819bf267… * [bundler](https://github.com/ruby/rubygems/blob/e4fd4ee3fad005fce1dbcbeffd47… * [textbringer](https://github.com/shugo/textbringer/blob/738d318558045efc9d97… -- https://bugs.ruby-lang.org/

5 7

[ruby-core:124209] [Ruby Feature#8948] Frozen regex
by Eregon (Benoit Daloze) 15 Dec '25

15 Dec '25

Issue #8948 has been updated by Eregon (Benoit Daloze). Right, it's too late for 4.0, OK. > Frankly, I don't think freezing the Regexp objects is worth the effort/trouble. I already did the implementation effort so that part is fine. I think it's worth it for consistency and clean semantics, it's much better to explain "all Regexp are frozen" rather than "Regexp is partially frozen, literals are frozen, non-literals are not, but semantically a Regexp is conceptually immutable, we only kept some instances mutable for some rare gems relying on it". Also TruffleRuby already enforce all Regexps to be frozen, so it's a way to be more compatible between Ruby implementations (it's basically infeasible to support a mix of mutable & non-mutable Regexps in TruffleRuby). And of course it's also good for Ractor where then we can say "all Regexps are shareable" vs "some are, some are not". It's just cleaner overall. > Here is the code we found in the dev meeting: Thanks. The `mongo-ruby-driver` is deprecated and seems of dubious value, I think it's not a big concern. I don't understand the use-case in `wallaby-rails`, it's called `LazyRegexp` but it creates the Regexp object eagerly. Also the `@lazy_source` ivar seems to just hold the source, which can be retrieved via `Regexp#source`. mame (Yusuke Endoh) wrote in #note-31: > Also, your PR changes the behavior of `Marshal.load` for a Regexp with encoding: > > ```diff > - assert_equal(/u/, Marshal.load("\004\bI/\a\\u\000\006:\016@encoding\"\vEUC-JP")) > + assert_raise(FrozenError) { Marshal.load("\004\bI/\a\\u\000\006:\016@encoding\"\vEUC-JP") } > ``` > > This incompatibility should be fixed. Also, as a general rule, please clearly state when a PR includes such known incompatibilities. Right, I should have left a comment about it on the PR, sorry. I think that is not reasonable to support, it's actually an `@encoding` ivar on the Regexp object which has no effect on `Regexp#encoding`: ``` irb(main):001> r=Marshal.load("\004\bI/\a\\u\000\006:\016@encoding\"\vEUC-JP") => /u/ irb(main):002> r.instance_variables => [:@encoding] irb(main):003> r.encoding => #<Encoding:US-ASCII> ``` Hence a FrozenError seems appropriate for that case. I would like to try this again in early 2026 / for Ruby 4.1. ---------------------------------------- Feature #8948: Frozen regex https://bugs.ruby-lang.org/issues/8948#change-115691 * 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