Rust Closure

A closure in Rust is an anonymous function capable of capturing variables from its enclosing lexical scope. Under the hood, the Rust compiler implements closures as anonymous, compiler-generated structs that store the captured environment, combined with an implementation of one or more of the callable traits (Fn, FnMut, or FnOnce).

Syntax and Type Inference

Closures are defined using pipe characters (|) to enclose parameters, followed by the closure body. Unlike standard functions (fn), closures do not strictly require explicit type annotations for parameters or return values.

// Fully annotated closure
let add_explicit = |x: i32, y: i32| -> i32 { x + y };

// Implicitly typed closure with expression body
let add_implicit = |x, y| x + y;

The compiler infers the types based on the closure’s first usage. Once inferred, the types are strictly locked. Invoking the same closure later with a different type results in a compilation error. Every closure instance has a unique, unnamable type, even if two closures have identical signatures and bodies.

Environment Capturing Mechanics

Rust automatically infers how a closure captures its environment based on the operations performed inside the closure body. The compiler defaults to the least restrictive capture method possible:

Immutable Borrow (&T): The closure only reads the captured variable.
Mutable Borrow (&mut T): The closure modifies the captured variable.
Ownership (T): The closure consumes the variable (e.g., moving it into a new allocation or dropping it).

You can explicitly force a closure to take ownership of its captured environment by prepending the move keyword. This is strictly a memory-transfer operation and does not dictate which callable trait the closure implements.

let data = vec![1, 2, 3];

// Forces 'data' to be moved into the closure's internal struct
let closure = move || {
    println!("{:?}", data); 
};
// 'data' is no longer accessible in the outer scope here

The Closure Traits

Because every closure has a unique type, passing closures as arguments or returning them requires generics bounded by one of three standard library traits. The compiler automatically implements these traits based on how the closure uses (reads, mutates, or consumes) the captured variables inside its body, regardless of how they were initially captured:

FnOnce: The closure can be called at least once. It is implemented by all closures. If a closure moves captured variables out of its environment (e.g., by dropping them or returning them), it only implements FnOnce and is consumed upon invocation.
FnMut: The closure can be called multiple times and is permitted to mutate its captured environment. Because Fn is a subtrait of FnMut, closures that only read their environment also implement FnMut.
Fn: The closure can be called multiple times without mutating its environment. It only requires shared, immutable access to its internal state.

// Accepts ANY closure that can be called at least once.
// Because Fn and FnMut are subtraits of FnOnce, this accepts closures 
// that consume, mutate, or strictly read their environment.
fn execute_once<F: FnOnce()>(f: F) {
    f();
}

// Accepts any closure that can be called multiple times.
// This includes closures that mutate their environment (FnMut) 
// and closures that only read their environment (Fn).
fn execute_mut<F: FnMut()>(mut f: F) {
    f();
}

// Accepts closures that can be called multiple times and strictly 
// only require shared, immutable access to their environment.
fn execute_shared<F: Fn()>(f: F) {
    f();
}

Compiler Desugaring

To understand closure memory layout, it is helpful to view how the compiler desugars them. When a closure captures variables, Rust generates a struct to hold those variables.

let a = 5;
let mut b = 10;
let c = String::from("Consume");

let closure = move || {
    b += a;
    drop(c);
};

Conceptually, the compiler translates the above closure into a struct and implements a callable interface. Because manual implementation of the Fn traits is unstable in Rust, the following valid Rust code uses a custom ConceptualFnOnce trait to accurately demonstrate the compiler’s internal mechanics:

// Compiler-generated anonymous struct representing the environment
struct ClosureEnvironment {
    a: i32,       // Copied (i32 implements Copy)
    b: i32,       // Copied (due to move keyword)
    c: String,    // Moved (String does not implement Copy)
}

// Conceptual representation of the standard library's FnOnce trait
trait ConceptualFnOnce {
    type Output;
    fn call_once(self) -> Self::Output;
}

// The compiler implements the callable trait for the generated struct.
// It takes `self` by value (consuming the struct) because 'c' is dropped inside.
impl ConceptualFnOnce for ClosureEnvironment {
    type Output = ();
    
    fn call_once(mut self) {
        self.b += self.a;
        drop(self.c);
    }
}

Tired of Poor Rust Skills? Fix That With Deep Grasping!Learn More

Functions

Traits

Closures

Generics

Enums

Pattern Matching

Structs

Macros

Lifetimes

Error Handling

Variables

Control Flow

Loops

Modules

Compound Types

Collection Types

Numeric Types

Text & Boolean Types

Attributes

Comments

Assignment Operators

Arithmetic Operators

Comparison Operators

Logical Operators

Unary Operators

Reference Operators

Access & Path Operators

Range Operators

Bitwise Operators

Type Cast Operators

Syntax and Type Inference

Environment Capturing Mechanics

The Closure Traits

Compiler Desugaring

​Syntax and Type Inference

​Environment Capturing Mechanics

​The Closure Traits

​Compiler Desugaring

Syntax and Type Inference

Environment Capturing Mechanics

The Closure Traits

Compiler Desugaring