You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@groovy.apache.org by "Christopher Smith (JIRA)" <ji...@apache.org> on 2015/06/14 02:56:00 UTC

[jira] [Created] (GROOVY-7468) type checker should use superclass bound when expected by generics

Christopher Smith created GROOVY-7468:
-----------------------------------------

             Summary: type checker should use superclass bound when expected by generics
                 Key: GROOVY-7468
                 URL: https://issues.apache.org/jira/browse/GROOVY-7468
             Project: Groovy
          Issue Type: Bug
          Components: Static Type Checker
    Affects Versions: 2.4.3
            Reporter: Christopher Smith
            Assignee: Cédric Champeau


I believe this is a special case of a general problem with generics and the type checker.

When I attempt to call a method {{doSomething(Map<String,Object> params)}} with a Groovy inline map, the type checker constructs the map's types as the immediate greatest-common-superclass of the values provided. For example, this map:

{code}
[ val1: 3, val2: 5 ]
{code}

is always considered to be a {{LinkedHashMap<String,Integer>}}, which can't be passed to the above method. In *some*, but not all, cases using an explicit {{as Map<String,Object>}} will work.

In the circumstance where an inline map or other generic collection is  assigned to a variable or used as a method parameter, the type checker should be able to relax the inferred generic type bound to match the expected bound.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)