[
https://issues.apache.org/jira/browse/GROOVY-7434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14558996#comment-14558996
]
ASF GitHub Bot commented on GROOVY-7434:
----------------------------------------
Github user asfgit closed the pull request at:
https://github.com/apache/incubator-groovy/pull/24
> Groovy should support resolving ambiguous signatures when using ClosureParams
> -----------------------------------------------------------------------------
>
> Key: GROOVY-7434
> URL: https://issues.apache.org/jira/browse/GROOVY-7434
> Project: Groovy
> Issue Type: Bug
> Reporter: Paul King
> Assignee: Paul King
> Fix For: 2.5.0-beta-1
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
