[GROOVY-6444] Closures are incorrectly coerced if a method call is done inside a closure

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 2.2.0
• Fix Version/s: 2.2.1
• Assignee: Cédric Champeau
• Reporter: Cédric Champeau
• Created: 22/Nov/13 06:39
• Updated: 26/Nov/13 14:48
• Resolved: 22/Nov/13 10:32

Description

The following test case demonstrates the problem:

Class foo(Runnable r) {
    // please do not remove wrapping inside a closure
    // because that's precisely what this test is supposed to check!
    { -> bar(r) }()
}

Class bar(Runnable r) {
   r.class
}

assert Closure.isAssignableFrom(foo { 'Hello' })

The assertion fails, with the class being a Proxy, which implies coercion to Runnable, which is implemented by Closure was involved.