Feature #11476: Methods defined in Refinements cannot be called via send

• Status: Closed
• Assignee: matz (Yukihiro Matsumoto)
• Target version: -

[matsuda (Akira Matsuda)]

class C end

module M
  refine C do
    def a() p:hello end
    def b() p:world end
  end
end

using M

C.new.a
C.new.send :b

% ruby -v t.rb
ruby 2.3.0dev (2015-08-22 trunk 51660) [x86_64-darwin14]
:hello
t.rb:13:in `<main>': undefined method `b' for #<C:0x007f86c9a12af0> (NoMethodError)

[shugo (Shugo Maeda)]

• Tracker changed from Bug to Feature
• Status changed from Open to Assigned
• Assignee changed from shugo (Shugo Maeda) to matz (Yukihiro Matsumoto)

It's an intended behavior that Kernel#send ignores refinements as described at https://bugs.ruby-lang.org/projects/ruby-trunk/wiki/RefinementsSpec

What do you think of it, Matz?

[matsuda (Akira Matsuda)]

Aah, I'm sorry that I missed that part of the documentation.
But indeed I felt the behaviour weird while using the feature in a real-world library.

[matz (Yukihiro Matsumoto)]

Accepted.

The current behavior is according to the direct interpretation of the refinement spec. But many people expect send to be another form of a method call (including refinement). And now I agree with it.

Matz

[shugo (Shugo Maeda)]

• Has duplicate Feature #12079: Loosening the condition for refinement added

[nobu (Nobuyoshi Nakada)]

• Status changed from Assigned to Closed

Applied in changeset r56450.

---

vm_insnhelper.c: refinements with send

• vm_insnhelper.c (vm_call_opt_send): enable refinements with
  Kernel#send and BasicObject#__send__. [Feature #11476]