Closure with typed arguments in Groovy

Adam Schmideg picture Adam Schmideg · Apr 15, 2011 · Viewed 9.5k times · Source

I'd like to be more explicit about my closures regarding their argument types. So I would write something like

List<Y> myCollect(List<X> list, Closure<X,Y> clos) { ... }

I know that Groovy won't use that type information, but Groovy++ may use it at compile time. Can this be be achieved (other than putting it into a comment)?

UPDATE: The title may sound misleading, but I thought the above example would make it clearer. I'm interested in specifying types of a closure which is the argument of some function. Suppose, I want to redefince the built-in collect. So I'm interested in writing myCollect, not in writing clos. What I want to achieve is get compile time errors

myCollect(['a', 'ab'], { it / 2 }) // compile error
myCollect(['a', 'ab'], { it.size() })  // OK 

Answer

D&#243;nal picture Dónal · Apr 18, 2011

You can define the types of a closure's parameters, but the syntax shown above is incorrect. Here is a closure without parameter types:

def concatenate = {arg1, arg2 ->
  return arg1 + arg2
}

And here is the same closure with parameter types

def concatenate = {String arg1, String arg2 ->
  return arg1 + arg2
}

I know that Groovy won't use that type information, but Groovy++ may use it at compile time.

Groovy does do some compile-time type checking, but not as much as Groovy++ (or Java). Even if the type information is not used at compile-time it will be checked at runtime, and is also valuable as a form of documentation.