[GROOVY-10820] SC: static choice of Class vs Object extension for Type dot name

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 4.0.7
• Assignee: Eric Milles
• Reporter: Eric Milles
• Created: 10/Nov/22 14:20
• Updated: 16/Oct/23 17:39
• Resolved: 23/Nov/22 16:14

Description

Consider the following:

@groovy.transform.CompileStatic
void test() {
  String.getMetaClass() // should refer to getMetaClass(Class)
  String.metaClass {}   // should refer to metaClass(Class,Closure)
  String.isCase(null)   // should refer to isCase(Class)
}

Static compiler is writing direct invoke of Object (or CharSequence for isCase) variants of examples above.

Issue Links

• is related to: GROOVY-4097 MOP implementation does not handle method calls in relation with class objects properly!
• is related to: GROOVY-7204 Static type checking and compilation fail when multiple generics in use
• is related to: GROOVY-10819 Meta class registry corruption leads to stack overflow
• relates to: GROOVY-10939 Non-static method java.lang.Object#hashCode cannot be called from static context
• relates to: GROOVY-11195 STC: false positive for Class method called from static context