[
https://issues.apache.org/jira/browse/GROOVY-11614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17946543#comment-17946543
]
Paul King commented on GROOVY-11614:
------------------------------------
Yes, that was the intent of the PR. I think that is worth doing for consistency
of the current behavior. If we also want to explore an option for dynamic
Groovy, I'd suggest cloning the issue. I believe the current changes are safe
for GROOVY_4_0_X. But a change to the delegation policy would be a breaking
change and would be 5 only. On this issue, we still have an optional
optimization we could do to limit walking the AST more than needed but the
obvious fix doesn't work. We can make that another issue too.
> Enums in switch/case statements that are not fully qualified will cause a
> groovy compile error but Java requires enums to "not" be fully qualified
> --------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: GROOVY-11614
> URL: https://issues.apache.org/jira/browse/GROOVY-11614
> Project: Groovy
> Issue Type: Bug
> Components: Compiler
> Affects Versions: 4.0.24, 5.0.0-alpha-12
> Reporter: Saravanan
> Priority: Minor
>
> This is a difference in Java vs Groovy behaviour. Enums must be fully
> qualified in Groovy while Java requires them to not be fully qualified.
> -This was supposedly fixed, but does not seem to work in 4.0.24. Not sure
> where it broke.-
> Example:
> {code:groovy}
> void test(Thread.State ts) {
> switch (ts) {
> case Thread.State.NEW: // cannot remove "Thread.State." without
> @CompileStatic
> break
> }
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
