Proc vs lambda differences (arity, return) in Ruby - Quick Revision & Key Differences

Recall & Review

beginner

What is a Proc in Ruby?

A Proc is a block of code that can be stored in a variable and called later. It behaves like a method but is more flexible and can be passed around.

intermediate

How does a lambda handle the number of arguments (arity) compared to a Proc?

A lambda checks the number of arguments strictly and raises an error if the count doesn't match. A Proc is more lenient and ignores extra arguments or assigns nil to missing ones.

intermediate

What happens when you use return inside a lambda vs inside a Proc?

Inside a lambda, return exits only from the lambda itself. Inside a Proc, return exits from the method enclosing the Proc, which can cause unexpected behavior.

beginner

Which behaves more like a method: Proc or lambda?

A lambda behaves more like a method because it checks arguments strictly and its return exits only from itself, not the enclosing method.

beginner

How do you create a lambda and a Proc in Ruby?

You create a lambda with lambda { |args| ... } or ->(args) { ... }. You create a Proc with Proc.new { |args| ... } or proc { |args| ... }.

What happens if you pass the wrong number of arguments to a lambda?

A It assigns nil to missing arguments

B It ignores extra arguments

C It runs without any checks

D It raises an error

A lambda strictly checks the number of arguments and raises an error if they don't match.

What does return inside a Proc do?

A Exits the enclosing method

B Exits only the Proc

C Raises an error

D Does nothing

A return inside a Proc exits the method that contains the Proc, not just the Proc itself.

Which one behaves more like a method in Ruby?

A lambda

B Neither

C Both behave the same

D Proc

A lambda behaves more like a method because it checks arguments and handles return differently.

How do you create a lambda in Ruby?

A Proc.new { ... }

B lambda { ... }

C def lambda ... end

D create_lambda { ... }

You create a lambda using the keyword lambda or the arrow syntax ->.

If a Proc receives fewer arguments than expected, what happens?

A It ignores missing arguments

B It raises an error

C It assigns nil to missing arguments

D It stops execution

A Proc assigns nil to any missing arguments instead of raising an error.

Explain the differences between Proc and lambda in Ruby regarding argument handling and return behavior.

Think about how each handles wrong number of arguments and where return goes.

Describe how you create and use a Proc and a lambda in Ruby with examples.

Show simple code snippets and explain behavior.

Practice

1. Which statement correctly describes the difference between a Proc and a lambda in Ruby regarding argument checking?

easy

A. Both Proc and lambda check arguments strictly.

B. Proc checks arguments strictly; lambda is lenient.

C. Neither Proc nor lambda check arguments.

D. Proc is lenient with arguments; lambda checks arguments strictly.

Solution

1. Step 1: Understand argument checking behavior

   A Proc in Ruby does not enforce the number of arguments strictly; it allows missing or extra arguments without error.

2. Step 2: Compare with lambda behavior

   A lambda behaves like a method and enforces the exact number of arguments, raising an error if the count is wrong.

3. Final Answer:

   Proc is lenient with arguments; lambda checks arguments strictly. -> Option D

4. Quick Check:

   Argument checking = Proc lenient, lambda strict [OK]

Hint: Remember: lambda acts like a method, Proc is more flexible [OK]

Common Mistakes:

• Thinking both check arguments strictly
• Confusing which one is strict
• Assuming Proc raises error on wrong args

2. Which of the following is the correct syntax to create a lambda in Ruby?

easy

A. lambda = Proc.new { |x| x * 2 }

B. lambda = proc { |x| x * 2 }

C. lambda = ->(x) { x * 2 }

D. lambda = lambda.new { |x| x * 2 }

Solution

1. Step 1: Identify lambda creation syntax

   In Ruby, lambdas can be created using the literal syntax ->(args) { block } or lambda { block }. The arrow syntax is common and concise.

2. Step 2: Check each option

   lambda = Proc.new { |x| x * 2 } creates a Proc, not a lambda. lambda = ->(x) { x * 2 } uses the correct lambda literal syntax. lambda = proc { |x| x * 2 } creates a Proc using proc. lambda = lambda.new { |x| x * 2 } is invalid syntax.

3. Final Answer:

   lambda = ->(x) { x * 2 } -> Option C

4. Quick Check:

   Lambda syntax = ->(args) { block } [OK]

Hint: Use ->(args) { } for lambda, Proc.new or proc for Proc [OK]

Common Mistakes:

• Using Proc.new when lambda is needed
• Trying lambda.new which doesn't exist
• Confusing proc and lambda syntax

3. What will be the output of the following Ruby code?

def test_proc
  p = Proc.new { return "From Proc" }
  p.call
  return "From method"
end

puts test_proc

medium

A. "From Proc"

B. "From method"

C. nil

D. RuntimeError

Solution

1. Step 1: Understand Proc return behavior

   When a Proc executes a return, it returns from the enclosing method, not just the Proc block.

2. Step 2: Trace the code execution

   Calling p.call triggers the Proc's return, which exits the test_proc method immediately with "From Proc". The later return "From method" is never reached.

3. Final Answer:

   "From Proc" -> Option A

4. Quick Check:

   Proc return exits method = "From Proc" [OK]

Hint: Proc return exits method; lambda return exits lambda only [OK]

Common Mistakes:

• Thinking return exits only the Proc block
• Expecting "From method" output
• Confusing Proc and lambda return behavior

4. Identify the error in the following Ruby code and fix it:

def test_lambda
  l = lambda { |x| return x * 2 }
  l.call
  return "Done"
end

puts test_lambda

medium

A. No error; output is "Done"

B. Error: lambda expects argument; fix by passing argument to l.call

C. SyntaxError: lambda block missing do/end

D. Error: lambda return exits method; fix by removing return inside lambda

Solution

1. Step 1: Check lambda argument requirements

   The lambda expects one argument x, but l.call is called without arguments, causing an ArgumentError.

2. Step 2: Fix the call by passing an argument

   Calling l.call(5) or any value fixes the error. The lambda returns x * 2, but this return exits only the lambda, so the method continues and returns "Done".

3. Final Answer:

   Error: lambda expects argument; fix by passing argument to l.call -> Option B

4. Quick Check:

   Lambda arity strict = pass correct args [OK]

Hint: Lambda needs exact args; always pass them when calling [OK]

Common Mistakes:

• Ignoring missing argument error
• Thinking lambda return exits method
• Assuming no arguments needed for lambda

5. Given the following code, what will be the output?

def test
  l = ->(x) { return x * 2 }
  p = Proc.new { return "Proc return" }
  result_l = l.call(3)
  result_p = p.call
  return "Method end"
end

puts test

hard

A. "Proc return"

B. "Method end"

C. 6

D. ArgumentError

Solution

1. Step 1: Execute lambda call

   The lambda l is called with argument 3, returns 6, but its return exits only the lambda, so method continues.

2. Step 2: Execute Proc call

   The Proc p is called next. Its return exits the entire method immediately with "Proc return". The later return "Method end" is never reached.

3. Final Answer:

   "Proc return" -> Option A

4. Quick Check:

   Proc return exits method, lambda return exits lambda [OK]

Hint: Proc return exits method immediately; lambda return does not [OK]

Common Mistakes:

• Expecting method to return "Method end"
• Confusing which return exits method
• Ignoring Proc's immediate method exit