It's be great to use groovy syntax to define new Groovy methods.
We'll probably need to use some kind of module feature for this.
Then later on we could use this module via
How it works
A module would be converted into a kind of class which implements some marker interface called 'Module' which could then use a static initializer to register the new methods on the MetaClass /MetaClass registry.
A simple implementation is for each use to install the new methods. If clashes or ordering issues happen we may want a way to have local copies of the MetaClass / MetaClassRegistry.
We could maybe have a static MetaClassRegistry instance inside each Module class which could be referenced in the bytecode explicitly when we invoke methods.
Then the class we compile with the use statements could store a static final reference to this MetaClassRegistry and refer to it when performing dynamic method dispatches.
We could also use this mechansims to add static (global) methods to the Module too. Another posibility is to apply pointcuts to a Module so we could use the Module abstraction for adding AOP advice?