[GROOVY-7434] Groovy should support resolving ambiguous signatures when using ClosureParams

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.5.0-alpha-1
• Component/s: Static Type Checker
• Assignee: Paul King
• Reporter: Paul King
• Created: 25/May/15 09:54
• Updated: 02/May/17 02:02
• Resolved: 26/May/15 12:10

Description

When using @ClosureParams annotated methods with @TC or @CS, if after applying type hints and built-in resolution based on number of parameters, generics analysis etc., more than one candidate signature is found, the usage will be flagged as ambiguous with a warning. It would be nice if instead a mechanism existed to resolve the ambiguity.

Issue Links

• is depended upon by: GROOVY-7433 API inconsistency between takeWhile, dropWhile and collectReplacements for CharSequences