[GROOVY-4945] Incorrect "Possible solutions" when calling a method on super in a non-derived class

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.7.10, 1.8.1, 2.4.0-rc-1
• Fix Version/s: 4.0.0-alpha-1, 3.0.5, 2.5.13
• Component/s: groovy-runtime
• Assignee: Eric Milles
• Reporter: Rene Scheibe
• Created: 25/Jul/11 06:09
• Updated: 23/Jul/20 14:16
• Resolved: 02/Jul/20 23:42

Description

Calling an instance method on super in a non-derived class.

class T { void m() { super.m() } }
new T().m() 

This results in the below exception.

ERROR groovy.lang.MissingMethodException:
No signature of method: T.m() is applicable for argument types: () values: []
Possible solutions: m(), is(java.lang.Object), dump(), any(), any(groovy.lang.Closure), use([Ljava.lang.Object;)

This can be quite confusion as the called method on super is also listed in the possible solutions. The error message should be a different one.

Calling a static method on super in a non-derived class.

class T { static void m() { super.m() } }
T.m() 

This results in the below stack overflow.

ERROR java.lang.StackOverflowError:
null
        at T.$getCallSiteArray (groovysh_evaluate)
        at T.m (groovysh_evaluate)
        at T.m (groovysh_evaluate:2)
        at T.m (groovysh_evaluate:2)
        ...

Issue Links

• is related to: GROOVY-9615 super.method() can trigger method on outer class in case of missing method