[ruby-core:93391] [Ruby trunk Bug#12131] Should defining singleton_method_added call itself?
From:
merch-redmine@...
Date:
2019-06-27 22:20:13 UTC
List:
ruby-core #93391
Issue #12131 has been updated by jeremyevans0 (Jeremy Evans). Given that `singleton_method_added` is called after the method is added and not before, I think the current behavior makes sense and do not think it is the bug. The same behavior exists for `method_added`: ```ruby module A extend self def method_added(n) p n end end ``` outputs: ``` :method_added ``` ---------------------------------------- Bug #12131: Should defining singleton_method_added call itself? https://bugs.ruby-lang.org/issues/12131#change-78925 * Author: Eregon (Benoit Daloze) * Status: Open * Priority: Normal * Assignee: * Target version: * ruby -v: ruby 2.2.2p95 (2015-04-13 revision 50295) [x86_64-linux] * Backport: 2.1: UNKNOWN, 2.2: UNKNOWN, 2.3: UNKNOWN ---------------------------------------- This seems surprising: ~~~ obj = Object.new def obj.singleton_method_added(n) p n end def obj.new_singleton_method; end ~~~ outputs ~~~ :singleton_method_added :new_singleton_method ~~~ -- https://bugs.ruby-lang.org/ Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>