Mutation of super to super() should not happen for a method with no arguments

[mvz]

(Follow-up from #309).

It looks like mutant wants to enforce super() as opposed to super, even when those two options are completely equivalent:

class Foo
  def bar
    # ...
  end
end

class Bar < Foo
  def bar
    # ...
    super
  end
end

Here, idiomatic Ruby would favor super over super(), but mutant wants me to use super(), and I see no way to write a spec to favor super.

[mbj]

@mvz I believe this is a duplicate of an existing issue we agreed upon fixing. Till I've the time to reference the original I'll keep it open.

I agree on fixing it, while you cite #309 I do not agree its at all the same case. Even when this statement may spark new discussions on #309. Please do not, I do not want to lock down another discussion, hint, hint, hint.

[dgollahon]

@mbj: I think this is the original issue for fixing super() when there are no arguments as it has been open for months (and i don't see another instance in the tracker). If it showed up in your github notifications again it is probably because I mistakenly commented on it last night (and then deleted my comment when I realized it was the wrong issue).

[mbj]

If it showed up in your github notifications again it is probably because I mistakenly commented on it last night (and then deleted my comment when I realized it was the wrong issue).

Hah, I was actually curious on why that old issue showed up. Thx for clearing that up for me.

[dgollahon]

Yeah, sorry about that xD