[jira] [Commented] (GROOVY-8837) Invalid type inference for redefined generic boundaries

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[jira] [Commented] (GROOVY-8837) Invalid type inference for redefined generic boundaries

JIRA jira@apache.org

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

Constantine Plotnikov commented on GROOVY-8837:
-----------------------------------------------

This specific maven configuration does use stubs, so it might be reverse:
{code:java}
<goal>generateStubs</goal>
<goal>compile</goal>
<goal>generateTestStubs</goal>
<goal>testCompile</goal>{code}

> Invalid type inference for redefined generic boundaries
> -------------------------------------------------------
>
>                 Key: GROOVY-8837
>                 URL: https://issues.apache.org/jira/browse/GROOVY-8837
>             Project: Groovy
>          Issue Type: Bug
>          Components: Compiler
>    Affects Versions: 2.5.2
>            Reporter: Constantine Plotnikov
>            Priority: Major
>         Attachments: groovy-bug-generic-extension.zip
>
>
> Static compiler incorrectly calculates type boundary for chain calls with generic types. When method is called, it takes boundary defined in the method of the class (Base in sample), instead of the boundary redefined in subclass (SubClass in sample).
> The bug was discovered when working with Lombok SuperBuilder generated classes from Groovy. The attached project demonstrate the bug on the smaller sample.
> Note that Java test infers type correctly, but groovy does not. However, the groovy test works when CompileStatic annotation is disabled.
> IDEA also shows red code here, but it possibly follows Groovy logic.
> The bug also affects earlier versions.



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