groovy

Usage of ".class" to disambiguate between methods

Details

  • Type: Improvement Improvement
  • Status: Open Open
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: 1.6.3
  • Fix Version/s: 3.0
  • Component/s: None
  • Labels:
    None
  • Testcase included:
    yes
  • Number of attachments :
    0

Description

From a programmer's perspective, it's clear that in the second example, Class.getName() should be called. Can we support this in 2.0?

class JavaLangClassUsageTest extends GroovyTestCase {
  void testCallFooGetNameMethod() {
    assert Foo.getName() == "Foo.getName" // passes
  }

  void testCallJavaLangClassGetNameMethod() {
    assert Foo.class.getName() == "Foo" // fails, actual: Foo.getName
  }
}

class Foo {
  static getName() { "Foo.getName" }
}

Issue Links

relates to

Bug - A problem which impairs or prevents the functions of the product. GROOVY-3548 Method call on instance of java.lang.Class is dispatched to equally named static method on class described by instance

  • Major - Major loss of function.
  • Open - The issue is open and ready for the assignee to start work on it.

Activity

Peter Niederwieser made changes -
Field Original Value New Value
Link This issue relates to GROOVY-3548 [ GROOVY-3548 ]

People

  • Assignee:
    Unassigned
    Reporter:
    Peter Niederwieser
Vote (0)
Watch (2)

Dates

  • Created:
    Updated: