[
https://issues.apache.org/jira/browse/GROOVY-8797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16618207#comment-16618207
]
Eric Milles commented on GROOVY-8797:
-------------------------------------
Thanks for the quick merge. Regarding your test case of overloads, is it
possible for the method-property loop to continue checking methods looking for
a better match? Or is that unneeded for proper compilation? In the IDE it
manifests as hover information that always refers to the first overload.
> VariableScopeVisitor.getPropertyName does not check for "isser" style method
> ----------------------------------------------------------------------------
>
> Key: GROOVY-8797
> URL: https://issues.apache.org/jira/browse/GROOVY-8797
> Project: Groovy
> Issue Type: Bug
> Affects Versions: 2.4.15, 3.0.0-alpha-3, 2.5.2
> Reporter: Eric Milles
> Assignee: Paul King
> Priority: Minor
> Fix For: 3.0.0-alpha-4, 2.5.3
>
>
> Consider the following:
> {code:groovy}
> class C {
> Object getFoo() {}
> boolean isBar() {}
> void setBaz(val) {}
> void method() {
> foo
> bar
> baz
> }
> }
> {code}
> {{VariableScopeVisitor}} returns a {{PropertyNode}} from {{findClassMember}}
> for {{foo}} and {{baz}}. However, the {{bar}} reference is seen as a
> {{MethodNode}}. {{VariableScopeVisitor.getPropertyName}} only checks for
> "get" and "set". Could it check for "is" and {{boolean}} return?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
