[GROOVY-7103] Allow static compliation when propertyMissing in extension

• Type: Improvement
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: 2.3.7
• Component/s: Static Type Checker
• Labels: @CompileStatic metaprogramming
• Environment: Any
• Assignee: Unassigned
• Reporter: Jochen Eddelbuettel
• Created: 05/Oct/14 02:18
• Updated: 20/Jan/16 18:42

Description

Arbitrary property names on Maps are treated as .get(propName) and work with @CompileStatic.

If a class itself or a registered extension provides propertyMissing implementations at compile time, those should be called in the compiler output. The return value of such implementations should be used to infer the type of the result of the property access. So with propertyMissing any class should be elevated to the same treatment as Map when it comes to @CompileStatic.

propertyMissing should behave the same as getAt/putAt operator overloading, again just like it does for Map.

So with

def propertyMissing(String propName)

{ getAt(propName) }

both obj.ANYPROP and obj["ANYPROP"] should allow static compilation.