Eric Milles created GROOVY-10124:
------------------------------------
Summary: Scope of class header (extends, implements and type
parameters) should not include class being declared
Key: GROOVY-10124
URL: https://issues.apache.org/jira/browse/GROOVY-10124
Project: Groovy
Issue Type: Bug
Reporter: Eric Milles
Similar to GROOVY-8063, the scope of the extends/implements clause is not
consistent with Java. Consider the following:
{code:groovy}
class C extends D {
class D {
}
}
{code}
Java compilers give an error like "D cannot be resolved to a type". Groovy
compiler resolves this without a qualifier. This is a problem for Java
integration (stubs, IDE, etc.) when the pre-resolved class (compile phase
CONVERSION) is used. This class compiles fine for Groovy but fails on the Java
side either by not being able to resolve D or giving a cyclic reference error
which groovy misses.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
