[GROOVY-3977] Auto-conversion inconsistency in BigDecimal treatment in method calls - Double vs Float

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.7.0
• Fix Version/s: 1.6.8, 1.7.1, 1.8-beta-1
• Assignee: Roshan Dawrani
• Reporter: Roshan Dawrani
• Created: 06/Jan/10 22:57
• Updated: 07/Apr/10 23:47
• Resolved: 07/Jan/10 02:19

Description

As reported by Peter on groovy user mailing list - :

class Foo {
 double myDouble
 float myFloat
}

def foo = new Foo()

// OK
foo.setMyDouble 0.1

/* groovy.lang.MissingMethodException: No signature of method: Foo.setMyFloat() 
is applicable for argument types: (java.math.BigDecimal) values: 0.1] */
foo.setMyFloat 0.1