[
https://issues.apache.org/jira/browse/GROOVY-11614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17945981#comment-17945981
]
ASF GitHub Bot commented on GROOVY-11614:
-----------------------------------------
eric-milles commented on PR #2199:
URL: https://github.com/apache/groovy/pull/2199#issuecomment-2817232959
They are already different. Switch statement supports unqualified enum
constants under STC. Switch expression does not. The expression case could be
made to work with delegation, in my estimation. It could be limited to STC as
well for the initial cut. Any other differences in behavior could be listed.
> 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)
