General

Profile

shugo (Shugo Maeda)

  • Login: shugo
  • Registered on: 05/08/2008
  • Last sign in: 05/12/2026

Issues

open closed Total
Assigned issues 2 156 158
Reported issues 4 82 86

Projects

Project Roles Registered on
Ruby Committer, Infrastructure team 05/28/2008

Activity

05/16/2026

12:24 AM Ruby Bug #22071: super in method in module that is refined results in NoMethodError
jeremyevans0 (Jeremy Evans) wrote in #note-3:
> ```diff
> ...
Thank you.
It seems reasonable except that `RCLASS_INCLUDER(me->defined_class)` is better than `((struct RClass_and_rb_classext_t*)me->defined_class)->classext.as.iclass.in...
shugo (Shugo Maeda)
12:09 AM Ruby Bug #22058: {Method,InstanceMethod}#super_method doesn't work correctly for refined method with refinements for method active in the caller's scope
jeremyevans0 (Jeremy Evans) wrote in #note-10:
> @shugo Thank you, I think I finally understand. After the first refinement method is called, the caller's scope no longer matters, because each `super` call site considers the refinements...
shugo (Shugo Maeda)

05/15/2026

04:50 AM Ruby Bug #22071 (Assigned): super in method in module that is refined results in NoMethodError
shugo (Shugo Maeda)
04:49 AM Ruby Bug #22071: super in method in module that is refined results in NoMethodError
Refinements for modules were initially prohibited, and were allowed in [Feature #12534] while `super` was still prohibited. Supporting `super` in a refinement for a module would go beyond a bug fix, so I think it should be discussed as a... shugo (Shugo Maeda)
02:38 AM Ruby Bug #22058: {Method,InstanceMethod}#super_method doesn't work correctly for refined method with refinements for method active in the caller's scope
jeremyevans0 (Jeremy Evans) wrote in #note-8:
> > > I think option 2 makes more sense, but it requires that Method/InstanceMethod objects for refined methods keep a reference to the scope in which they were created
> ...
`Kernel#method...
shugo (Shugo Maeda)

05/14/2026

07:01 AM Ruby Bug #22058: {Method,InstanceMethod}#super_method doesn't work correctly for refined method with refinements for method active in the caller's scope
jeremyevans0 (Jeremy Evans) wrote:
> I think option 2 makes more sense, but it requires that Method/InstanceMethod objects for refined methods keep a reference to the scope in which they were created
Could you clarify what you mean by "...
shugo (Shugo Maeda)

05/13/2026

08:34 AM Ruby Bug #22058: {Method,InstanceMethod}#super_method doesn't work correctly for refined method with refinements for method active in the caller's scope
matz (Yukihiro Matsumoto) wrote in #note-4:
> @shugo is right. The change in super's behavior in 2.7 was unintentional, so I'm in favor of fixing it to match the documentation.
I realized that completely ignoring refinements when sea...
shugo (Shugo Maeda)
05:40 AM Ruby Bug #22058 (Assigned): {Method,InstanceMethod}#super_method doesn't work correctly for refined method with refinements for method active in the caller's scope
shugo (Shugo Maeda)
01:37 AM Ruby Bug #22058: {Method,InstanceMethod}#super_method doesn't work correctly for refined method with refinements for method active in the caller's scope
shugo (Shugo Maeda) wrote in #note-2:
> FYI, I tried using rb_callable_method_entry_without_refinements() in method_super_method() to avoid the infinite loop, but it returns a wrong result in the following case:
Actually, I need to r...
shugo (Shugo Maeda)

05/12/2026

08:50 AM Ruby Bug #22058: {Method,InstanceMethod}#super_method doesn't work correctly for refined method with refinements for method active in the caller's scope
jeremyevans0 (Jeremy Evans) wrote:
> These semantics seem questionable. My guess is they are not the result of intentional design, but due purely to implementation details. I see two possibilities:
> ...
Agreed.
FYI, I tried using r...
shugo (Shugo Maeda)

Also available in: Atom