Groovy Closure delegate and owner scoping limits

Groovy Closures utilize two distinct properties to manage execution context: the owner and the delegate. While the owner provides a reference to the scope where the Closure was defined, the delegate allows the redirection of method resolution to a different object at runtime, which is a core mechanism for building Domain Specific Languages (DSLs).

A design challenge arises when both properties are set, as the method resolution order determines whether a call is dispatched to the delegate or the owner. This dynamic dispatch can create ambiguity in complex environments where the delegate and owner share similar method signatures or property names.

• How does Groovy prioritize method resolution when a method exists on both the delegate and the owner?
• What are the specific constraints on modifying the owner property compared to the delegate after a Closure has been instantiated?