Forum: Ruby-core Feature Proposal: Method#super_method

5a837592409354297424994e8d62f722?d=identicon&s=25 unknown (Guest)
on 2014-05-02 01:11
(Received via mailing list)
Issue #9781 has been updated by Ryan Davis.


Maybe it is just me misunderstanding something... but this doesn't seem
that complicated. I don't understand why you'd walk through the
ancestors when you just just ask one level up:

~~~ruby
class BigFoo
  def bar
  end
end

class Foo < BigFoo
  def bar
    super
  end
end

class Object
  def super_method name
    self.class.superclass.instance_method name
  end
end

p Foo.new.method(:bar).source_location.last                           #
=> 7
p Foo.new.class.superclass.instance_method(:bar).source_location.last #
=> 2
p Foo.new.super_method(:bar).source_location.last                     #
=> 2
~~~

----------------------------------------
Feature #9781: Feature Proposal: Method#super_method
https://bugs.ruby-lang.org/issues/9781#change-46435

* Author: Richard Schneeman
* Status: Open
* Priority: Normal
* Assignee:
* Category: core
* Target version:
----------------------------------------

When `super` is called in a method the Ruby VM knows how to find the
next ancestor that has that method and call it. It is difficult to do
this manually, so I propose we expose this information in
Method#super_location.

Ruby Method class (http://www.ruby-doc.org/core-2.1.1/Method.html) is
returned by calling Object.method and passing in a method name
(http://www.ruby-doc.org/core-2.1.1/Object.html#met...). This
is useful for debugging:

```ruby
# /tmp/code.rb
class Foo
  def bar
  end
end

puts Foo.new.method(:bar).source_location
# => ["/tmp/code.rb", 3]
```

The Object#method allows a ruby developer to easily track the source
location of the method and makes debugging very easy. However if the
code is being invoked by a call to `super` it is difficult to track
down:

```ruby
# /tmp/code.rb

class BigFoo
  def bar
  end
end

class Foo < BigFoo
  def bar
    super
  end
end
```

In this code sample it is easy to find the method definition inside of
Foo but it is very difficult in large projects to find what code exactly
`super` is calling. This simple example is easy, but it can be hard when
there are many ancestors. Currently if I wanted to find this we can
inspect ancestors

```ruby
Foo.ancestors[1..-1].map do |ancestor|
  next unless ancestor.method_defined?(:bar)
  ancestor.instance_method(:bar)
end.compact.first.source_location
```

To make this process simpler I am proposing a method on the Method class
that would return the result of `super`


It could be called like this:

```ruby
Foo.new.method(:bar).super_method
```

I believe adding Method#super_method, or exposing this same information
somewhere else, could greatly help developers to debug large systems
easily.
This topic is locked and can not be replied to.