[
https://issues.apache.org/jira/browse/GROOVY-7490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Milles updated GROOVY-7490:
--------------------------------
Fix Version/s: 2.5.22
> CompileStatic confuses statically importing an instance and statically
> importing a method
> -----------------------------------------------------------------------------------------
>
> Key: GROOVY-7490
> URL: https://issues.apache.org/jira/browse/GROOVY-7490
> Project: Groovy
> Issue Type: Bug
> Components: Static compilation
> Affects Versions: 2.4.3
> Reporter: Robert Elliot
> Assignee: Eric Milles
> Priority: Major
> Fix For: 4.0.0-beta-2, 2.5.22, 3.0.16
>
>
> 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.
> {code:java}
> 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"
> }
> }
> {code}
> 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.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
