Understanding Groovy Closures
Learn the concept of closures, how to define them, and their versatile applications in Groovy.
Understanding Groovy Closures is a free Groovy & Gradle: JVM Automation and Build Engineering lesson on CoddyKit — lesson 2 of 4. You can read the complete lesson below for free — then practise it hands-on in the browser with a built-in code editor and a 24/7 AI tutor. It is part of the Groovy & Gradle: JVM Automation and Build Engineering learning path, one of 4 lessons in the course, and your progress syncs across the web and the CoddyKit app.
What Are Groovy Closures?
Welcome to the world of Groovy closures! A closure is essentially a block of code that can be treated like a variable.
Think of it as a mini-function you can define, store, and pass around. Closures are a powerful feature that make Groovy code very flexible and concise.
- They are first-class citizens, meaning they can be assigned to variables, passed as arguments, and returned from methods.
- They can capture variables from their surrounding scope, even after that scope has finished executing.
Basic Closure Syntax
Defining a closure is straightforward. You enclose your code block within curly braces {}. Let's see a simple example:
class Main {
static void main(String[] args) {
// Define a simple closure
def sayHello = {
println "Hello from a closure!"
}
// Call (execute) the closure
sayHello()
}
}Closures with Parameters
Just like methods, closures can accept parameters. You list the parameters before the -> (arrow) operator, followed by the closure's body.
This allows your closure to perform operations based on the input it receives.
class Main {
static void main(String[] args) {
// Closure that takes two parameters
def add = { num1, num2 ->
return num1 + num2
}
// Call the closure with arguments
def result = add(10, 5)
println "Sum: ${result}"
// You can also omit 'return' for the last statement
def multiply = { a, b -> a * b }
println "Product: ${multiply(4, 3)}"
}
}The 'it' Keyword
When a closure takes exactly one parameter, Groovy provides a special implicit variable called it. You don't need to declare it explicitly.
This makes single-parameter closures even more concise and readable, especially when used with collection methods.
class Main {
static void main(String[] args) {
// Closure using 'it' for a single parameter
def square = { it * it }
println "Square of 7: ${square(7)}"
def greetPerson = { "Hello, ${it}!" }
println greetPerson("Alice")
}
}Closures as Method Arguments
One of the most common and powerful uses of closures in Groovy is passing them as arguments to methods. Many Groovy methods, especially those on collections, are designed to accept closures.
If a closure is the last argument to a method, you can place it outside the parentheses, making the code look very clean and DSL-like.
class Main {
static void main(String[] args) {
def numbers = [1, 2, 3, 4, 5]
// Using 'each' with a closure to iterate
numbers.each { num ->
println "Number: ${num}"
}
println "---"
// Using 'collect' with a closure to transform
def doubledNumbers = numbers.collect { it * 2 }
println "Doubled: ${doubledNumbers}"
}
}Capturing Variables: Lexical Scope
Closures have lexical scope, meaning they remember and can access variables from the scope where they were defined, even if that scope no longer exists.
This is a key characteristic that differentiates closures from regular methods and allows them to carry context with them.
class Main {
static void main(String[] args) {
def name = "Groovy User" // Variable in the outer scope
def introduce = {
// The closure 'introduce' captures 'name'
println "My name is ${name}."
}
introduce() // Calls the closure, accessing 'name'
name = "CoddyKit Enthusiast" // Change the outer variable
introduce() // The closure still references the updated 'name'
}
}Modifying Captured Variables
Not only can closures access captured variables, but they can also modify them. This creates a powerful way for closures to interact with their surrounding environment.
Be mindful when modifying external variables from within closures, as it can sometimes lead to less predictable code if not managed carefully.
class Main {
static void main(String[] args) {
def counter = 0 // A variable to be captured
def increment = {
counter++ // Closure modifies the outer 'counter'
println "Counter is now: ${counter}"
}
increment() // Counter: 1
increment() // Counter: 2
increment() // Counter: 3
println "Final counter value: ${counter}"
}
}Closure 'call()' Method
While you can execute a closure by simply using parentheses (e.g., myClosure()), closures are actually instances of the groovy.lang.Closure class.
This means they also have a call() method. Using call() is equivalent to direct execution and can sometimes be useful for clarity or when dynamically invoking closures.
class Main {
static void main(String[] args) {
def greet = { name ->
println "Hello, ${name}!"
}
// Direct execution
greet("World")
// Execution using the call() method
greet.call("Groovy")
def add = { a, b -> a + b }
println add.call(5, 7)
}
}Practical Use: Filtering Lists
Let's put closures to work with a practical example: filtering elements from a list. Groovy's collection methods, like findAll, are perfect for this.
You provide a closure that defines the condition for inclusion, and findAll returns a new list containing only the elements that satisfy that condition.
class Main {
static void main(String[] args) {
def numbers = [10, 25, 12, 30, 5, 45, 20]
// Find numbers greater than 20
def largeNumbers = numbers.findAll { it > 20 }
println "Numbers > 20: ${largeNumbers}"
// Find even numbers
def evenNumbers = numbers.findAll { it % 2 == 0 }
println "Even numbers: ${evenNumbers}"
}
}Closure Concepts Check
Which of the following statements about Groovy Closures are TRUE?
Recap: Understanding Closures
Great job! You've taken a significant step in understanding Groovy's powerful closures.
Here's a quick summary of what we covered:
- Closures are code blocks treated as first-class citizens.
- They use
{}for definition and->for parameters. - The
itkeyword simplifies single-parameter closures. - Closures are often passed as method arguments, enhancing Groovy's expressiveness.
- They possess lexical scope, capturing and even modifying variables from their surrounding context.
In the next lesson, we'll explore how to apply closures to functional programming patterns in Groovy!
Frequently asked questions
Is the “Understanding Groovy Closures” lesson free?
Yes — the full text of “Understanding Groovy Closures” is free to read here on the web, and the Groovy & Gradle: JVM Automation and Build Engineering course includes 4 lessons in total. To practise it interactively (a built-in code editor and a 24/7 AI tutor) and unlock the rest of the Groovy & Gradle: JVM Automation and Build Engineering course, upgrade to CoddyKit PRO.
What will I learn in “Understanding Groovy Closures”?
Learn the concept of closures, how to define them, and their versatile applications in Groovy. You practise Groovy & Gradle: JVM Automation and Build Engineering with hands-on code you run directly in the browser, and a 24/7 AI tutor answers your questions as you work through the lesson.
Do I need any experience to start Groovy & Gradle: JVM Automation and Build Engineering?
No prior experience is required. Groovy & Gradle: JVM Automation and Build Engineering on CoddyKit is structured for beginners through advanced learners; this is — lesson 2 of 4, so you can start here or from the beginning and move at your own pace.
How long does the “Understanding Groovy Closures” lesson take?
Most CoddyKit lessons take about 5–10 minutes. Each one is bite-sized and interactive, so you make steady progress and pick up exactly where you left off across the web and the app.
Can I write and run code in this Groovy & Gradle: JVM Automation and Build Engineering lesson?
Yes. Every Groovy & Gradle: JVM Automation and Build Engineering lesson includes a built-in code editor, so you write and run real code right in your browser and get instant AI feedback — no local setup required.
All lessons in this course
- Groovy Collections Enhancements
- Understanding Groovy Closures
- Functional Patterns with Groovy
- Currying & Composing Closures