Many Kernel methods are defined as Object methods about rbs HOT 6 CLOSED

Thank you for the comment. It seems we can call super with top-level redefinitions. Interesting.

p method(:puts)
#=> #<Method: Object(Kernel)#puts(*)>

def puts(*)
  print "before\n"
  super
  print "after\n"
end

puts "hello"
#=> before
#=> hello
#=> after

p method(:puts)
#=> #<Method: Object#puts(*) t.rb:1>

p method(:puts).super_method
#=> #<Method: Kernel#puts(*)>

from rbs.

That’s a Ruby implementation problem ¯\_(ツ)_/¯

Object.instance_methods(false) #=> []

Everything is actually all defined in Kernel, with Object merely BasicObject + Kernel.
The API docs put instance methods (as opposed to utility functions like print) on the Object page for our convenience (read: façade). RBS just followed suit.

P.S. IMO, those methods listed should not only be on Object’s RBS page, but also actually define under Object rather than Kernel, as Object is a class and Kernel sounds more like a utils package. Unfortunately, it’s probably all hard-to-refactor ancient code at this point.

from rbs.

I found this PR. #86

@soutaro
Do you still think the same way?
I am concerned about the meaning of RBS as a document.

from rbs.

+1 for moving those methods to ::Kernel. (But when?)

When #86 was composed, we didn't have %a{annotate:rdoc:copy:???} annotation. But today we have, and we can have the RBS definitions in Kernel while it copies the docs form Object methods.

The doc says:

Object クラスのメソッドは実際にはこのモジュールで定義されています。これはトップレベルでのメソッドの再定義に対応するためです。 https://docs.ruby-lang.org/ja/latest/class/Kernel.html

(I cannot find the english version.) Methods of Object class are actually defined in this module. This is for over-writing methods in top-level.

So, for this purpose, RBS definition should be in Kernel module too. (While it's not very clear to me what it means... Does it mean we can call the originals with super ??)

from rbs.

(I cannot find the english version.)

Although the instance methods of Object are defined by the Kernel module, we have chosen to document them here for clarity.
⸺ Object

Truthfully, [P.S. given that it’s probably all hard-to-refactor ancient code at this point,] I too prefer everything defined under Kernel to document in Kernel to represent how things are done. But Team Core had reasons.
In the mean time, I also prefer RBS to match the Ruby docs (whether they decide Object or Kernel) for consistency.

from rbs.