Scott Murphy Heiberg created GROOVY-12604:
---------------------------------------------
Summary: A promoted trait static that calls a @Virtual static
fails with MissingMethodException when called through the trait
Key: GROOVY-12604
URL: https://issues.apache.org/jira/browse/GROOVY-12604
Project: Groovy
Issue Type: Bug
Affects Versions: 6.0.0
Reporter: Scott Murphy Heiberg
{code:groovy}
import groovy.transform.Virtual
trait T {
@Virtual static String setting() { 'default' }
static String describe() { 'setting=' + setting() }
}
class C implements T {}
assert C.describe() == 'setting=default'
assert T.describe() == 'setting=default'
{code}
Actual: {{T.describe()}} throws {{MissingMethodException: No signature of
static method: setting for class: T is applicable for argument types: ()
values: []}}. This happens in dynamic Groovy, with @TypeChecked and with
@CompileStatic. The trait documentation's own @Virtual example fails the same
way when called as {{Configurable.describe()}}.
Expected: called through the trait itself there is no implementing class, so
the trait's own (default) implementation of the @Virtual static is used, and
the call returns {{setting=default}}.
Public trait statics are promoted to the trait interface, and the forwarder
passes the trait interface as the static self. The @Virtual call site
dispatches dynamically on that self, but @Virtual statics are deliberately not
promoted to the interface, so the call finds nothing.
Seen in 6.0.0 (the first version with @Virtual).
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
