[
https://issues.apache.org/jira/browse/GROOVY-11492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18133603#comment-18133603
]
ASF GitHub Bot commented on GROOVY-11492:
-----------------------------------------
eric-milles commented on PR #3054:
URL: https://github.com/apache/groovy/pull/3054#issuecomment-6471318219
@daniellansun
re point 2: The goal was to move `Object[] a = { {} }` forward from a NPE to
something usable. If there are still cases of mismatched dimensions, those
could be filed as separate bugs.
re point 3: I looked at the other similar failure messages and found the new
error location more consistent than the previous behavior.
re point 4: An email was sent to the dev list.
> Java compatibility: array initializers without "new Type[]"
> -----------------------------------------------------------
>
> Key: GROOVY-11492
> URL: https://issues.apache.org/jira/browse/GROOVY-11492
> Project: Groovy
> Issue Type: Improvement
> Components: parser-antlr4
> Reporter: Eric Milles
> Assignee: Eric Milles
> Priority: Major
> Labels: arrays
>
> There are a few cases where bare array initializers are not yet supported:
> # {{int[][] array = \{ \{1,2\}, \{3,4\} \};}}
> # {{@Target(\{ ElementType.FIELD, ElementType.METHOD \})}}
> # {code:groovy}@interface A {
> String[] strings() default {}
> }
> {code}
> These were implemented as part of [1] but the PR was closed. It may be worth
> looking back over what was done and re-implementing one or more of these
> cases. It was noted that {{Closure[] array = \{\};}} is one of the edge
> cases that leads to ambiguity.
> [1] https://github.com/apache/groovy/pull/691
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
