Details
-
Type:
Sub-task
-
Status:
Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: 1.1-rc-3
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
-
Number of attachments :
Description
This is related to the GString equality issues, but is an issue on its own.
This might cause nasty side effects. BigDecimal a = 2.0 BigDecimal b = 2.00 println a.equals(b) // false println(a.compareTo(b)) // 0 println a == b // true println([a].equals([b])) // true, which is different from Java, which would return false!
I think Groovy should try to behave 100 percent like Java in such contexts.
I changed the version fix version to 1.2 since this is a design issue rather than a bug and we won't change that for 1.1