You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@groovy.apache.org by "Eric Milles (JIRA)" <ji...@apache.org> on 2019/04/26 15:38:00 UTC

[jira] [Updated] (GROOVY-9097) STC: different errors for map[k] and map.getAt(k)

     [ https://issues.apache.org/jira/browse/GROOVY-9097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Eric Milles updated GROOVY-9097:
--------------------------------
    Component/s: Static Type Checker

> STC: different errors for map[k] and map.getAt(k)
> -------------------------------------------------
>
>                 Key: GROOVY-9097
>                 URL: https://issues.apache.org/jira/browse/GROOVY-9097
>             Project: Groovy
>          Issue Type: Bug
>          Components: Static Type Checker
>            Reporter: Eric Milles
>            Priority: Major
>
> Follow up to GROOVY-6668.  Explicit {{getAt}} call produces different error from square-bracket version.  Could they both produce the same error?  I prefer "Cannot call ... with arguments [groovy.lang.GString]" over the recently introduced "Cannot find matching method ..."
> {code:groovy}
> @groovy.transform.CompileStatic
> void meth() {
>   def key = "${'key'}"
>   Map<String, String> map = [:]
>   map[key].toUpperCase() // Cannot find matching method java.lang.Object#toUpperCase(). Please check if the declared type is correct and if the method exists.
>   map.getAt(key).toUpperCase() // Cannot call <K,V> java.util.LinkedHashMap <java.lang.String, java.lang.String>#getAt(java.lang.String) with arguments [groovy.lang.GString] 
> }
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)