GRECLIPSE

Class with overloaded static and instance method with Map parameter is underlined at call site

Details

  • Type: Bug Bug
  • Status: Open Open
  • Priority: Minor Minor
  • Resolution: Unresolved
  • Affects Version/s: 2.6.0.Release
  • Fix Version/s: None
  • Component/s: Compiler Integration, Editor
  • Labels:
    None
  • Number of attachments :
    0

Description

In the following script:

ClassWithOverloadedStaticInstanceMethod.method(from: "2011-01-01", to: "2011-01-31")

class ClassWithOverloadedStaticInstanceMethod {
    static method(Map params){}
    def method() {}
}

The callsite appears as ClassWithOverloadedStaticInstanceMethod.method(from: "2011-01-01", to: "2011-01-31") in the editor. It appears as though this is related to the special Map syntax since changing the code slightly resolves the issue:

def params = [from: "2011-01-01", to: "2011-01-31"]
ClassWithOverloadedStaticInstanceMethod.method(params)

class ClassWithOverloadedStaticInstanceMethod {
    static method(Map params){}
    def method() {}
}

Activity

Hide
Permalink
Andrew Eisenberg added a comment -

Here's what's happening:

  1. Inferencing engine must choose between the static and non-static variants of the methods.
  2. Since the number of arguments is 2, and inferencing engine only matches based on argument number, it arbitrarily chooses the non-static variant
  3. Since the non-static variant is used in a static context, it is underlined. The assumption is that invoking this non-static method in a static context will cause a runtime error.

The bug here is that we are only looking at number of parameters, but since this is a named parameter list, we should be able to know that we are looking for the method variant that takes a map.

Show
Andrew Eisenberg added a comment - Here's what's happening: Inferencing engine must choose between the static and non-static variants of the methods. Since the number of arguments is 2, and inferencing engine only matches based on argument number, it arbitrarily chooses the non-static variant Since the non-static variant is used in a static context, it is underlined. The assumption is that invoking this non-static method in a static context will cause a runtime error. The bug here is that we are only looking at number of parameters, but since this is a named parameter list, we should be able to know that we are looking for the method variant that takes a map.

People

  • Assignee:
    Unassigned
    Reporter:
    Bob Tiernay
Vote (0)
Watch (0)

Dates

  • Created:
    Updated: