[
https://issues.apache.org/jira/browse/GROOVY-7734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15170489#comment-15170489
]
Anton commented on GROOVY-7734:
-------------------------------
I get it. The thing is, I needed such functionality and this is how I stumbled
upon this method so I ended up implementing it myself. Is there any special
policy regarding such stuff? I mean keeping a method which is probably not used
vs. deleting it vs. fixing the implementation. Thanks
> ClassNode tryFindPossibleMethod only defined for TupleExpression
> ----------------------------------------------------------------
>
> Key: GROOVY-7734
> URL: https://issues.apache.org/jira/browse/GROOVY-7734
> Project: Groovy
> Issue Type: Bug
> Affects Versions: 2.4.5
> Reporter: Anton
>
> As seen here
> https://github.com/apache/groovy/blob/master/src/main/org/codehaus/groovy/ast/ClassNode.java#L1257-L1258
> if {{arguments}} is not a {{TupleExpression}} the method just returns.
> Shouldn't this be defined for other expression types as well?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
