Backport #8284
closedExpected behavior of Module#public_class_method
Description
It was pointed out by Myron Marston (here: https://gist.github.com/myronmarston/5401829) that calling public_class_method on an anonymous module makes the named method public on Object, etc.
Object.define_method => NoMethodError
Module.new.public_class_method(:define_method)
Object.define_method => ArgumentError
Also of note, the same is not true when calling it on a class:
Object.define_method => NoMethodError
Class.new.public_class_method(:define_method)
Object.define_method => NoMethodError
which seems inconsistent given:
Module.new.singleton_class.ancestors => [Module, Object, Kernel, BasicObject]
Class.new.singleton_class.ancestors => [Class, Module, Object, Kernel, BasicObject]
Is this a bug or expected behavior? If the latter, what is the correct explanation?