[jira] [Commented] (GROOVY-9064) STC: explicit declared variable type ignored in favor of assigned value type(s)

["Eric Milles (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/GROOVY-9064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16983633#comment-16983633 ] 

Eric Milles commented on GROOVY-9064:
-------------------------------------

See also GROOVY-7763

> STC: explicit declared variable type ignored in favor of assigned value type(s)
> -------------------------------------------------------------------------------
>
>                 Key: GROOVY-9064
>                 URL: https://issues.apache.org/jira/browse/GROOVY-9064
>             Project: Groovy
>          Issue Type: Improvement
>            Reporter: Eric Milles
>            Priority: Major
>
> Follow up to GROOVY-9058.  Consider the following:
> {code:groovy}
> List getSomeRows() { ... }
> @groovy.transform.CompileStatic
> void meth() {
>   List<Object[]> rows = getSomeRows()
>   rows.each { row ->
>     def col = row[0]
>   }
> }
> {code}
> The inferred type of {{rows}} is {{List}} and not {{List<Object[]>}} even though the assignment cleared type checking.  This causes the inferred type of {{row}} to be {{Object}} instead of {{Object[]}}.
> Similarly, {{List<String> list = []}} infers as {{ArrayList<String>}} instead of the explicit declared type, and {{Map<String, ?> map = [:]}} infers to {{LinkedHasMap<...>}} instead of the declared type.  In general, I think as long as the assignment is compatible, the variable should retain its explicitly declared type regardless of assignments.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)