[GROOVY-7868] Calling super constructor with in-line casted Closure param does not compile: unexpected "constructor call must be first statement" error

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 2.4.6
• Fix Version/s: 3.0.0-beta-3
• Component/s: Compiler
• Environment: Linux Mint 17.3
• Assignee: Daniel Sun
• Reporter: Jordan Martinez
• Created: 19/Jun/16 00:07
• Updated: 11/Nov/20 02:01
• Resolved: 31/Oct/19 23:54

Description

Running the following code in Groovy Console should result "successfully" with "Could not find matching constructor for 'SomeObject'"

Instead, code fails with issue "Constructor call must be the first statement in a constructor," which is weird because it is...

Code only runs correctly (e.g. fails in the expected way) in 5 cases:

• "{} as BiConsumer" line in the super constructor is commented out
• all arguments past Closure-cast line must be commented out
• Closure is cast to a different object (say String)
• the first "Collections.emptyList()" is changed to a different type (say String) but the second remains the same
• The BiConsumer's second generic type (Collection<String>) is changed to a different type (say String)

import java.util.function.BiConsumer

public class ProblematicObject extends SomeObject {

    public ProblematicObject() {
        super(
            { } as BiConsumer<String, Collection<String>>, 
            
            Collections.emptyList(),
            Collections.emptyList()
        )
    }
    
}

new ProblematicObject()