DEV Community

Cover image for Understanding Lambda Functions in Ruby
Davide Santangelo
Davide Santangelo

Posted on • Updated on

Understanding Lambda Functions in Ruby

Lambda functions, also known as anonymous functions or lambda expressions, play an important role in many programming languages, including Ruby. In this article, we will delve into the concept of lambda functions in Ruby, exploring their syntax, use cases, and benefits.

What are Lambda Functions?

Lambda functions are a concise way to define anonymous functions, which means functions without a name. In Ruby, lambda functions are instances of the Proc class. They are defined using the lambda keyword or the -> (stabby lambda) syntax.

# Using the lambda keyword
my_lambda = lambda { |x| x * 2 }

# Using the stabby lambda syntax
my_lambda = ->(x) { x * 2 }
Enter fullscreen mode Exit fullscreen mode

Both examples above create a lambda function that takes a single argument x and returns its doubled value.

Syntax and Usage

The basic syntax of a lambda function includes the keyword (lambda or ->), a list of parameters, and the code block. The code block contains the logic of the function.

# Lambda with multiple parameters
sum_lambda = ->(a, b) { a + b }

# Calling the lambda
result =, 5)
puts result  # Output: 8
Enter fullscreen mode Exit fullscreen mode

Lambda functions can be assigned to variables, passed as arguments to other functions, and returned from functions, making them a powerful tool for creating modular and flexible code.

# Passing a lambda as an argument
def operate_on_numbers(a, b, operation), b)

add_lambda = ->(x, y) { x + y }
result = operate_on_numbers(4, 7, add_lambda)
puts result  # Output: 11
Enter fullscreen mode Exit fullscreen mode

Key Differences from Procs and Methods

While lambda functions in Ruby share similarities with Procs and methods, there are subtle differences. One notable distinction is in how they handle the return keyword.

# Using a lambda with return
my_lambda = ->(x) { return x * 2 }

# Using a Proc with return
my_proc = { |x| return x * 2 }
Enter fullscreen mode Exit fullscreen mode

If you call a lambda that contains a return statement, it will only exit the lambda and continue with the surrounding code. In contrast, a return statement inside a Proc will exit the entire method enclosing it.

Advantages of Lambda Functions

  1. Conciseness: Lambda functions allow you to write compact and expressive code, particularly when passing functions as arguments.

  2. Flexibility: They provide a flexible way to encapsulate behavior, making it easy to reuse and compose functions in different contexts.

  3. Closures: Lambdas, like Procs, capture the surrounding scope, enabling them to retain access to variables outside their own scope.

  4. Functional Programming: Lambda functions are fundamental in functional programming paradigms, facilitating the use of higher-order functions.

Drawbacks and Considerations

While lambda functions in Ruby offer many advantages, it's crucial to be aware of certain drawbacks and considerations when incorporating them into your code.

  1. Readability: Although lambda functions can make code concise, excessive use or complex logic within a lambda may lead to reduced readability. It's essential to strike a balance between brevity and clarity, ensuring that code remains understandable to other developers.

  2. Limited Use Cases: Lambda functions are best suited for short, simple operations. For more extensive and complex functionality, regular methods might be a better choice. Using lambdas for everything could result in code that is harder to maintain and understand.

  3. Debugging Complexity: Debugging can be more challenging with lambda functions compared to regular methods. Since lambdas are anonymous and lack explicit names, identifying the source of issues might be trickier, especially in larger codebases.

  4. Performance Overhead: While the performance differences are often negligible, as mentioned earlier, in certain scenarios, such as high-frequency operations, the overhead of invoking lambda functions might become a concern. Careful consideration is needed when optimizing for performance.

  5. Lack of Explicit Return: Lambda functions use an implicit return, meaning the value of the last expression evaluated is automatically returned. This can be confusing in certain situations, especially for developers accustomed to methods with explicit return statements.

# Implicit return in lambda
multiply_lambda = ->(x, y) { x * y }

# Explicit return in a regular method
def multiply(x, y)
  return x * y
Enter fullscreen mode Exit fullscreen mode
  1. Compatibility: While lambda functions are available in modern Ruby versions, if you are working on a legacy codebase or with older Ruby versions, compatibility might be a concern. Ensure that the Ruby version used in your project supports the lambda syntax.

Performance Considerations

When it comes to performance, it's essential to consider the overhead introduced by using lambda functions compared to other approaches like regular methods. While the differences might be negligible in many cases, understanding the implications can help make informed decisions based on the specific requirements of your code.

Lambda functions introduce a slight overhead due to their dynamic nature and the fact that they are instances of the Proc class. Calling a lambda involves a method invocation, which might be marginally slower than invoking a regular method directly. However, it's crucial to note that the performance impact is often minimal and might not be noticeable in most applications.

In scenarios where performance is a critical concern, especially within tight loops or high-frequency operations, developers might choose to opt for regular methods. Ruby methods are optimized by the interpreter, and their direct invocation tends to be faster than invoking a lambda.

# Regular method
def double(x)
  x * 2

# Lambda function
double_lambda = ->(x) { x * 2 }

# Performance comparison
require 'benchmark'

n = 1_000_000 do |x|'Regular Method:') { n.times { double(5) } }'Lambda Function:') { n.times { } }
Enter fullscreen mode Exit fullscreen mode
user     system      total        real
Regular Method:  0.046488   0.000004   0.046492 (  0.046494)
Lambda Function:  0.048329   0.000005   0.048334 (  0.048362)
[#<Benchmark::Tms:0x0000000127fecef0 @cstime=0.0, @cutime=0.0, @label="Regular Method:", @real=0.04649400000926107, @stime=3.9999999999901226e-06, @total=0.046491999999999964, @utime=0.046487999999999974>,
 #<Benchmark::Tms:0x0000000127fec1f8 @cstime=0.0, @cutime=0.0, @label="Lambda Function:", @real=0.04836199997225776, @stime=5.0000000000050004e-06, @total=0.048334000000000016, @utime=0.04832900000000001>] 
Enter fullscreen mode Exit fullscreen mode

The Benchmark module is used here to compare the performance of invoking a regular method versus a lambda function. Keep in mind that these differences may vary based on the Ruby interpreter and version.

In practice, it's recommended to prioritize code readability and maintainability over micro-optimizations unless you're working on a performance-critical application. The choice between lambda functions and regular methods should be made based on the context and design goals, with an understanding that the performance differences are generally minor in typical use cases.

Ruby On Rails

In the context of Ruby on Rails, a lambda function, commonly referred to simply as a lambda, is a type of anonymous function used to define blocks of code that can be stored in variables or passed as arguments to methods.

While Rails primarily leverages Ruby's inherent support for lambdas, their use within the framework is particularly prevalent in various aspects such as callbacks, validations, and scopes. Lambdas provide a concise and flexible way to encapsulate behavior, allowing developers to encapsulate reusable snippets of code that can be executed dynamically. For example, in Rails models, lambdas are often used within scopes to dynamically define query conditions, contributing to the expressive and modular nature of Rails code. Their ability to enforce argument count and controlled return behavior makes lambdas a powerful tool for encapsulating behavior in Rails applications, promoting code readability, maintainability, and reusability.

Below is an example that demonstrates the use of a lambda function in a Rails model. In this example, a post model is defined with a scope that uses a lambda to filter posts based on a condition.

# Assuming you have a `Post` model in your Rails application

class Post < ApplicationRecord
  # Example lambda function used in a scope
  scope :published, -> { where(published: true) }

  # Other model code...

Enter fullscreen mode Exit fullscreen mode

In this example, the published scope uses a lambda function to define a condition for retrieving only the posts where the published attribute is set to true. This is a simplified example, and you can customize the lambda to suit your specific needs. Scopes are commonly used to encapsulate reusable query logic in Rails models.

You can then use this scope in your code like this:

# Retrieve all published posts
published_posts = Post.published
Enter fullscreen mode Exit fullscreen mode

This will return a collection of Post instances that satisfy the conditions specified in the lambda function within the scope. The use of lambdas in this context contributes to the clarity and flexibility of the Rails codebase.


Lambda functions in Ruby provide a powerful and flexible way to write concise, modular, and expressive code. Their ability to be treated as first-class citizens makes them valuable in various programming scenarios, improving the readability and maintainability of your code. As you continue to explore Ruby, consider adding lambda functions to your programming toolkit for a more elegant and efficient coding experience.

Top comments (3)

nirebu profile image
Nicolò Rebughini

Great writeup!

demo318 profile image
Devin Mork

This was super helpful. I've been using scopes in Rails but had never commented the dots that those were lambda functions.

stojakovic99 profile image
Nikola Stojaković

Good article, just one small correction.

Lambda functions use an implicit return, meaning the value of the last expression evaluated is automatically returned.

This is the case for methods too; in the example you gave you could have omitted return.