IMO, we should compare their type first. If not same, the comparing result should be 'false'.

Cheers,
Daniel.Sun



在 "bo zhang [via Groovy]" <ml-node+[hidden email]>,2016年11月3日 06:53写道:

I'm afraid it's not a bug.

Actually, `def a=new int[2][]` means that a is an array of two null pointers with type "int []", and `def b=new int[2][][]` means that b is an array of two null pointers with type "int[][]", it seems that they should be equal.

See https://github.com/groovy/groovy-core/blob/master/src/test/groovy/ArrayTest.groovy#L198




2016-10-30 18:50 GMT+08:00 Daniel.Sun <[hidden email]>:
Hi Jochen,

     I create JIRA issue
GROOVY-7983(https://issues.apache.org/jira/browse/GROOVY-7983) to track the
issue.

     BTW,  the code in the email should be corrected as follow:

def a = new int[2][]
def b = new int[2][][]
assert a == b // expect faling

Cheers,
Daniel.Sun



--
View this message in context: http://groovy.329449.n5.nabble.com/An-issue-about-comparing-arrays-tp5736379p5736398.html
Sent from the Groovy Dev mailing list archive at Nabble.com.




If you reply to this email, your message will be added to the discussion below:
http://groovy.329449.n5.nabble.com/An-issue-about-comparing-arrays-tp5736379p5736458.html
To unsubscribe from An issue about comparing arrays, click here.
NAML


View this message in context: Re: An issue about comparing arrays
Sent from the Groovy Dev mailing list archive at Nabble.com.