[
https://issues.apache.org/jira/browse/GROOVY-7434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14558144#comment-14558144
]
ASF GitHub Bot commented on GROOVY-7434:
----------------------------------------
GitHub user paulk-asert opened a pull request:
https://github.com/apache/incubator-groovy/pull/24
GROOVY-7434: Groovy should support resolving ambiguous signatures whe…
…n using ClosureParams
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/paulk-asert/incubator-groovy groovy7434
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-groovy/pull/24.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #24
----
commit 343282d2faa471d79615d1af50aeba09d81cc841
Author: Paul King <pa...@asert.com.au>
Date: 2015-05-25T11:49:08Z
GROOVY-7434: Groovy should support resolving ambiguous signatures when
using ClosureParams
----
> 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)
