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

ASF GitHub Bot commented on GROOVY-6787:
----------------------------------------

GitHub user fpavageau opened a pull request:

    https://github.com/apache/groovy/pull/221

    GROOVY-6787 Compare arguments with the generic bounds

    The type inference on arguments shouldn't override the types of the
    parameters, especially their bounds. This prevented the bound checks from
    occurring.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/fpavageau/groovy GROOVY-6787

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/groovy/pull/221.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #221
    
----
commit 5cb1a6119279895f877ba82144c34675e70f8aeb
Author: Frank Pavageau <[email protected]>
Date:   2015-12-22T21:47:40Z

    GROOVY-6787 Compare arguments with the generic bounds
    
    The type inference on arguments shouldn't override the types of the
    parameters, especially their bounds. This prevented the bound checks from
    occurring.

----


> type checker does not check generics bounds of wildcards properly
> -----------------------------------------------------------------
>
>                 Key: GROOVY-6787
>                 URL: https://issues.apache.org/jira/browse/GROOVY-6787
>             Project: Groovy
>          Issue Type: Bug
>          Components: Static Type Checker
>    Affects Versions: 2.2.2, 2.3.0, 2.4.0-rc-1
>            Reporter: Jochen Theodorou
>
> {code:Java}
> public <T extends List<CharSequence>> void bar(T a){}
> bar([new Object()])
> {code}
> This should not compile because Object is no CharSequence, but it does, 
> because the type checker will simply ignore the bound and set T to 
> LinkedList<Object>



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

Reply via email to