From: "rosenfeld (Rodrigo Rosenfeld Rosas)" <rr.rosas@...>
Date: 2012-06-26T00:47:27+09:00
Subject: [ruby-core:45836] [ruby-trunk - Feature #4254] Allow method transplanting


Issue #4254 has been updated by rosenfeld (Rodrigo Rosenfeld Rosas).


I guess it wouldn't make much sense and would lead to other developer's confusion as the method may rely on some internal state of an instance of that class...
----------------------------------------
Feature #4254: Allow method transplanting
https://bugs.ruby-lang.org/issues/4254#change-27414

Author: zimbatm (Jonas Pfenniger)
Status: Closed
Priority: Normal
Assignee: matz (Yukihiro Matsumoto)
Category: core
Target version: 2.0.0


=begin
Is there a technical reason to not allow re-binding a method from one module to any other module ?
 
  module M
    def foo; "foo"; end
  end

  module N; end
  N.send(:define_method, :foo, M.instance_method(:foo)) #=> should not raise
 
It's like monkey-patching. Powerful, dangerous, but also really useful. It could allow different variations of method_wrap or alias_method_chain that are not possible right now.
=end



-- 
http://bugs.ruby-lang.org/