[
https://issues.apache.org/jira/browse/GROOVY-11614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17997754#comment-17997754
]
Paul King commented on GROOVY-11614:
------------------------------------
The following script works for me (on master):
{code:groovy}
@groovy.transform.CompileStatic
class RecordTesting {
enum Thing {
ME,
YOU
}
String create(Thing a) {
switch (a) {
case ME: return "STR"
case YOU: return "YOU"
}
return ""
}
}
assert new RecordTesting().create(RecordTesting.Thing.ME) == 'STR'
{code}
Do you have an AST transform that might be altering the AST to be something
different from what Groovy is expecting?
When I run this in the GroovyConsole and invoke Script -> Inspect AST, I see
the transformed code that looks like this:
{code:groovy}
case RecordTesting$Thing.ME:
return 'STR'
{code}
Do you see something different in your environment?
> 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
> Assignee: Paul King
> Priority: Minor
> Fix For: 5.0.0-beta-1, 4.0.27
>
>
> 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)
