[GROOVY-7490] CompileStatic confuses statically importing an instance and statically importing a method

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.4.3
• Fix Version/s: 4.0.0-beta-2, 2.5.22, 3.0.16
• Component/s: Static compilation
• Assignee: Eric Milles
• Reporter: Robert Elliot
• Created: 02/Jul/15 23:38
• Updated: 16/May/23 13:31
• Resolved: 25/Oct/21 16:49

Description

When statically importing a field and immediately calling a call() method on it, the static compiler gets confused and looks for a static method with the name of the field that takes the arguments passed to the call() method.

See below - comment out @CompileStatic and it will run as expected.

import groovy.transform.CompileStatic

class WithCall {

    static final WithCall staticallyImported = new WithCall()

    String call(String input) {
        return input;
    }
}

class CompileStaticImport {

    @CompileStatic
    public static void main(String[] args) {
        assert WithCall.staticallyImported("to print") == "to print"
    }
}

Error:(16, 16) Groovyc: [Static type checking] - Cannot find matching method WithCall#staticallyImported(java.lang.String). Please check if the declared type is right and if the method exists.

Issue Links

• is related to: GROOVY-8389 Static import of a property messes with instance method
• relates to: GROOVY-11056 modified behavior of variable resolution within Closure