Ruby Issue Tracking System

11/14/2026

01:16 AM Ruby Feature #18915: New error class: NotImplementedYetError or scope change for NotImplementedError

@zverok Thank you for the feedback, but I am going to keep `AbstractMethodError` under `ScriptError`.
A missing implementation of an abstract method is a defect in the class definition, not a runtime condition to recover from. I don't... matz (Yukihiro Matsumoto)

12:44 AM Ruby Feature #22530: Deprecate fractional day support for Date

I agree. `Date` represents a day, so it should not carry a fraction of a day, and the inconsistency between the constructors and `+`/`-` is confusing. Please go ahead with the proposed schedule.
Matz. matz (Yukihiro Matsumoto)

12:32 AM Ruby Misc #22506: Clarify read-only, lock and freeze in IO::Buffer

I agree with the proposed model. But before going further, I'd like to hear the opinion from @ioquatix first.
Matz. matz (Yukihiro Matsumoto)

11/13/2026

08:52 AM Ruby Feature #22244: `ruby -UU` should set both internal and external, `ruby -E` should print encoding list

For now, I agree with @naruse. The internal encoding is for automatic conversion, and setting `LANG` properly is the recommended way, so I don't see the need for `-UU` to set both.
For the other points, `Encoding.name_list` already gi... matz (Yukihiro Matsumoto)

08:45 AM Ruby Feature #22523: define_method should make its body shareable when possible, using Ractor.shareable_proc semantics

I agree with the direction. As discussed at the developers' meeting, the concern is the impact on existing code unrelated to Ractor, which is hard to estimate in advance.
So let's merge this after the December release and experiment w... matz (Yukihiro Matsumoto)

08:40 AM Ruby Feature #22520: {Proc,Method,UnboundMethod}#syntax_tree should return the block node, not the enclosing call

Accepted. `#syntax_tree` should return the node for the code the object actually runs, so for a block it should be the block node, consistent with `#source_range` (#21998). Please go ahead while the method is still experimental.
One r... matz (Yukihiro Matsumoto)

08:33 AM Ruby Feature #22483: Region forms of String#bit_get

The region forms of `bit_get` are accepted as proposed.
Regarding the write counterpart, I am fine with `bit_put`. I understand @mame's point that get/set is the usual pair in Ruby. But in bit manipulation, "set" already means turning... matz (Yukihiro Matsumoto)

04:40 AM Ruby Feature #22482: String#bit_index, a bit search for String bit operations

Accepted. `String#bit_index` is a good answer to the concerns I raised in #22399. One search primitive is much easier to accept than seven methods, the name follows `String#index`, and the measurements show it is worth having, including ... matz (Yukihiro Matsumoto)

11/12/2026

02:26 PM Ruby Bug #22462: For UnboundMethod, super_method.bind and bind.super_method should return an equal Method

I agree with the proposed invariant: `um.bind(o).super_method == um.super_method.bind(o)`. Please go ahead, on top of the fix for #22505.
Regarding the point @shugo raised, I accept that `UnboundMethod#==` and `Method#==` differ here.... matz (Yukihiro Matsumoto)

01:41 PM Ruby Bug #22505: UnboundMethod#{bind,bind_call} results in incorrect behavior when method owner is at multiple places in ancestry

I agree this is a bug. An `UnboundMethod` taken from `C` should start method lookup from the position of `C` in the ancestry, so `[:m, :c]` is the expected result. Please go ahead with the fix.
Since the current behavior dates back to... matz (Yukihiro Matsumoto)