You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@groovy.apache.org by "Daniel Sun (JIRA)" <ji...@apache.org> on 2018/05/17 16:58:00 UTC
[jira] [Resolved] (GROOVY-6167) Generics: within a single
declaration, generic type definition order matters
[ https://issues.apache.org/jira/browse/GROOVY-6167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Sun resolved GROOVY-6167.
--------------------------------
Resolution: Fixed
Assignee: Daniel Sun
Fix Version/s: 2.5.0-rc-3
3.0.0-alpha-3
2.6.0-alpha-4
Fixed by https://github.com/apache/groovy/commit/48807d5b1ba094e2f0dc212b6c92b4b370fe8394
> Generics: within a single declaration, generic type definition order matters
> ----------------------------------------------------------------------------
>
> Key: GROOVY-6167
> URL: https://issues.apache.org/jira/browse/GROOVY-6167
> Project: Groovy
> Issue Type: Bug
> Components: Compiler
> Affects Versions: 2.1.0, 2.4.0-beta-3
> Reporter: Davide Cavestro
> Assignee: Daniel Sun
> Priority: Major
> Fix For: 2.6.0-alpha-4, 3.0.0-alpha-3, 2.5.0-rc-3
>
>
> The following is valid Java code, but the groovyc fails complaining
> {color:red}_unable to resolve class X_
> {color}
> {code:java}
> public class Foo<T extends List<X>, X extends Number>{}
> {code}
> while changing the generic type definition order it works
> {code:java}
> public class Foo<X extends Number, T extends List<X>>{}
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)