[
https://issues.apache.org/jira/browse/GROOVY-9064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Milles updated GROOVY-9064:
--------------------------------
Component/s: Static Type Checker
> 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: Bug
> Components: Static Type Checker
> Reporter: Eric Milles
> Assignee: Eric Milles
> Priority: Major
> Fix For: 4.0.0-alpha-3, 3.0.9
>
>
> 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.20.10#820010)
