Keyword arguments in Ruby - Time & Space Complexity

Time Complexity: Keyword arguments

O(1)

Understanding Time Complexity

When using keyword arguments in Ruby methods, it's important to understand how the method's execution time changes as input grows.

We want to see how the time to run the method changes when we pass different numbers or sizes of keyword arguments.

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

def greet(name:, greeting: "Hello", punctuation: "!")
  puts "#{greeting}, #{name}#{punctuation}"
end

greet(name: "Alice", greeting: "Hi")

This method uses keyword arguments to print a greeting message. It takes a name, an optional greeting, and an optional punctuation mark.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: The method simply uses the keyword arguments to build a string and print it once.
• How many times: The method runs its code once per call, with no loops or repeated traversals inside.

How Execution Grows With Input

Explain the growth pattern intuitively.

Input Size (number of keyword args)	Approx. Operations
3	Few operations to build and print string
10	Still a few operations; each extra keyword arg adds a small fixed cost
100	Operations grow linearly but remain small since no loops process all keywords

Pattern observation: The time grows slowly and roughly in a straight line with the number of keyword arguments, but since the method does not loop over them, the cost stays very low.

Final Time Complexity

Time Complexity: O(1)

This means the method runs in constant time regardless of how many keyword arguments are passed, because it does not loop or process them repeatedly.

Common Mistake

[X] Wrong: "More keyword arguments always make the method slower in a big way."

[OK] Correct: Keyword arguments are passed as a hash, but if the method does not loop through them, the time to access each is constant and does not add up significantly.

Interview Connect

Understanding how keyword arguments affect performance helps you write clear and efficient methods, a skill useful in many coding situations.

Self-Check

"What if the method looped through all keyword arguments to print each one? How would the time complexity change?"

Practice

1. What is the purpose of keyword arguments in Ruby methods?

easy

A. To convert all arguments into strings automatically

B. To force all arguments to be passed in order

C. To make arguments optional without default values

D. To allow passing arguments by name for clarity and flexibility

Solution

1. Step 1: Understand keyword arguments

   Keyword arguments let you pass values to a method by naming them, not just by position.

2. Step 2: Identify the benefit

   This makes code clearer and lets you skip or reorder arguments easily.

3. Final Answer:

   To allow passing arguments by name for clarity and flexibility -> Option D

4. Quick Check:

   Keyword arguments = named, clear, flexible [OK]

Hint: Keyword arguments are named for clarity and order freedom [OK]

Common Mistakes:

• Thinking keyword arguments force order
• Confusing keyword arguments with positional arguments
• Assuming keyword arguments convert types automatically

2. Which of the following is the correct syntax to define a method with keyword arguments in Ruby?

easy

A. def greet(name =>, age =>); puts "Hello #{name}, you are #{age}"; end

B. def greet(name, age); puts "Hello #{name}, you are #{age}"; end

C. def greet(name:, age:); puts "Hello #{name}, you are #{age}"; end

D. def greet(name =:, age =:); puts "Hello #{name}, you are #{age}"; end

Solution

1. Step 1: Review Ruby keyword argument syntax

   Keyword arguments are defined with a colon after the argument name, like name:.

2. Step 2: Check each option

   def greet(name:, age:); puts "Hello #{name}, you are #{age}"; end uses correct syntax with name: and age:. Others use invalid symbols or positional arguments.

3. Final Answer:

   def greet(name:, age:); puts "Hello #{name}, you are #{age}"; end -> Option C

4. Quick Check:

   Keyword args use colon after name [OK]

Hint: Keyword args end with colon in method definition [OK]

Common Mistakes:

• Using => instead of : for keyword arguments
• Defining keyword arguments without colons
• Confusing positional and keyword argument syntax

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

def info(name:, age: 30)
  "Name: #{name}, Age: #{age}"
end

puts info(name: "Alice")

medium

A. Name: Alice, Age: 30

B. Name: Alice, Age:

C. ArgumentError: missing keyword: age

D. Name: , Age: 30

Solution

1. Step 1: Analyze method parameters

   The method info has a required keyword argument name: and an optional keyword argument age: with default 30.

2. Step 2: Check method call

   The call passes name: "Alice" but no age, so default 30 is used.

3. Final Answer:

   Name: Alice, Age: 30 -> Option A

4. Quick Check:

   Default keyword argument used when missing [OK]

Hint: Missing keyword uses default if provided [OK]

Common Mistakes:

• Expecting error when optional keyword is missing
• Confusing positional defaults with keyword defaults
• Ignoring default values in keyword arguments

4. Identify the error in the following Ruby method call:

def order(item:, quantity:)
  "Order: #{quantity} x #{item}"
end

puts order(quantity: 3, "apple")

medium

A. ArgumentError: missing keyword: item

B. SyntaxError due to positional argument after keyword argument

C. No error, prints 'Order: 3 x apple'

D. TypeError: wrong argument type String (expected Symbol)

Solution

1. Step 1: Examine method call arguments

   The call uses quantity: 3 (keyword) then "apple" (positional).

2. Step 2: Understand Ruby argument rules

   In Ruby, positional arguments cannot come after keyword arguments in a call; this causes a syntax error.

3. Final Answer:

   SyntaxError due to positional argument after keyword argument -> Option B

4. Quick Check:

   Positional args must come before keyword args [OK]

Hint: Positional args cannot follow keyword args in calls [OK]

Common Mistakes:

• Passing positional argument after keyword argument
• Assuming Ruby allows mixed order without error
• Confusing missing keyword with syntax error

5. Given this method:
<pre>def build_profile(name:, age:, city: "Unknown", **extras) profile = {name: name, age: age, city: city} profile.merge!(extras) profile end What will be the result of build_profile(name: "Bob", age: 25, hobby: "guitar", pet: "dog")?

hard

A. {:name=>"Bob", :age=>25, :city=>"Unknown", :hobby=>"guitar", :pet=>"dog"}

B. {:name=>"Bob", :age=>25, :city=>"Unknown"}

C. ArgumentError: unknown keyword: hobby

D. {:name=>"Bob", :age=>25, :city=>"Unknown", :extras=>{:hobby=>"guitar", :pet=>"dog"}}

Solution

1. Step 1: Understand method parameters

   The method requires name and age, has optional city with default, and collects extra keyword arguments into extras.

2. Step 2: Analyze method call

   The call passes name, age, and extra keywords hobby and pet. These extras are merged into the profile hash.

3. Step 3: Determine final hash

   The returned hash includes all keys: name, age, default city, plus hobby and pet from extras.

4. Final Answer:

   {:name=>"Bob", :age=>25, :city=>"Unknown", :hobby=>"guitar", :pet=>"dog"} -> Option A

5. Quick Check:

   Extras merged into hash with defaults [OK]

Hint: Use **extras to capture and merge extra keyword args [OK]

Common Mistakes:

• Expecting error on unknown keywords with **extras
• Forgetting to merge extras into profile
• Assuming extras stored under :extras key