You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@groovy.apache.org by "Paul King (JIRA)" <ji...@apache.org> on 2017/05/02 02:03:05 UTC

[jira] [Closed] (GROOVY-7434) Groovy should support resolving ambiguous signatures when using ClosureParams

     [ https://issues.apache.org/jira/browse/GROOVY-7434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Paul King closed GROOVY-7434.
-----------------------------

> 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
>          Components: Static Type Checker
>            Reporter: Paul King
>            Assignee: Paul King
>             Fix For: 2.5.0-alpha-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.15#6346)