Array slicing and ranges in Ruby - Time & Space Complexity

Time Complexity: Array slicing and ranges

O(k)

Understanding Time Complexity

When we use array slicing and ranges in Ruby, we want to know how the time it takes grows as the array gets bigger.

We ask: How does the work change when we slice bigger parts of the array?

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

arr = (1..1000).to_a
slice = arr[100..199]

This code creates an array of 1000 numbers and then slices out 100 elements from it using a range.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Copying elements from the original array to the new slice.
• How many times: Once for each element in the slice range.

How Execution Grows With Input

When the slice size grows, the work grows in the same way because each element is copied once.

Input Size (slice length)	Approx. Operations
10	10 copies
100	100 copies
1000	1000 copies

Pattern observation: The number of operations grows directly with the slice size.

Final Time Complexity

Time Complexity: O(k)

This means the time grows linearly with the number of elements you slice out.

Common Mistake

[X] Wrong: "Slicing an array is always a constant time operation."

[OK] Correct: Because Ruby creates a new array and copies each element in the slice, so the time depends on how many elements you take.

Interview Connect

Understanding how slicing works helps you explain efficiency when working with parts of arrays, a common task in coding challenges and real projects.

Self-Check

"What if we used a single index instead of a range for slicing? How would the time complexity change?"

Practice

1. What does the expression arr[1..3] do when arr = [10, 20, 30, 40, 50]?

easy

A. Returns a new array with elements at indexes 1, 2, and 3

B. Returns a new array with elements at indexes 1 and 3 only

C. Returns a new array with elements at indexes 1 and 2 only

D. Returns a single element at index 3

Solution

1. Step 1: Understand the range operator '..'

   The range 1..3 includes both 1 and 3, so it covers indexes 1, 2, and 3.

2. Step 2: Apply slicing to the array

   Slicing arr[1..3] returns elements at indexes 1, 2, and 3, which are 20, 30, and 40.

3. Final Answer:

   Returns a new array with elements at indexes 1, 2, and 3 -> Option A

4. Quick Check:

   Range '..' includes end index = elements 20, 30, 40 [OK]

Hint: Remember '..' includes the end index in slicing [OK]

Common Mistakes:

• Thinking '..' excludes the end index
• Confusing indexes with values
• Assuming slicing changes the original array

2. Which of the following is the correct syntax to get elements from index 2 up to but not including index 5 in Ruby array arr?

easy

A. arr[2...5]

B. arr[2:5]

C. arr[2..5]

D. arr[2-5]

Solution

1. Step 1: Identify the range operator for excluding end

   In Ruby, ... excludes the end index, so 2...5 means indexes 2, 3, and 4.

2. Step 2: Check syntax correctness

   Only arr[2...5] uses valid Ruby syntax for slicing excluding the end index.

3. Final Answer:

   arr[2...5] -> Option A

4. Quick Check:

   Use '...' to exclude end index in range [OK]

Hint: Use '...' to exclude the last index in range slicing [OK]

Common Mistakes:

• Using '..' when exclusion is needed
• Using Python-style slicing syntax like ':'
• Using invalid range syntax like '2-5'

3. What is the output of the following Ruby code?

arr = [5, 10, 15, 20, 25]
slice = arr[1...4]
puts slice.inspect

medium

A. [10, 15, 20, 25]

B. [15, 20, 25]

C. [10, 15, 20]

D. [5, 10, 15]

Solution

1. Step 1: Understand the slicing range

   The range 1...4 includes indexes 1, 2, and 3 but excludes 4.

2. Step 2: Extract elements at these indexes

   Elements at indexes 1, 2, 3 are 10, 15, and 20 respectively.

3. Final Answer:

   [10, 15, 20] -> Option C

4. Quick Check:

   Range '...' excludes end index = [10, 15, 20] [OK]

Hint: Remember '...' excludes the last index in slicing [OK]

Common Mistakes:

• Including element at index 4 mistakenly
• Confusing indexes with values
• Printing original array instead of slice

4. Identify the error in the following Ruby code snippet:

arr = [1, 2, 3, 4, 5]
slice = arr[2..6]
puts slice.inspect

medium

A. Syntax error due to invalid range

B. Range end index 6 is out of bounds but Ruby returns elements up to the end of the array

C. Runtime error because index 6 does not exist

D. slice will be empty array because range is invalid

Solution

1. Step 1: Check the range indexes against array size

   The array has indexes 0 to 4. The range 2..6 goes beyond the last index.

2. Step 2: Understand Ruby slicing behavior for out-of-bounds

   Ruby returns elements from index 2 to the end (indexes 2, 3, 4) and ignores indexes beyond 4 without error.

3. Final Answer:

   Range end index 6 is out of bounds but Ruby returns elements up to the end of the array -> Option B

4. Quick Check:

   Ruby slices safely even if range exceeds array size [OK]

Hint: Ruby slicing ignores out-of-bound indexes without error [OK]

Common Mistakes:

• Expecting runtime or syntax error
• Assuming slice will be empty
• Confusing Ruby with other languages that error here

5. Given arr = [2, 4, 6, 8, 10, 12], which expression returns a new array with every second element starting from index 1 up to index 5?

hard

A. arr[1..5].select.with_index { |_, i| i.even? }

B. arr[1..5].select.with_index { |_, i| i.odd? }

C. arr[1...6].values_at(*arr[1...6].each_index.select(&:even?))

D. arr[1..5].values_at(*arr[1..5].each_index.select(&:odd?))

Solution

1. Step 1: Slice array from index 1 to 5

   arr[1..5] gives [4, 6, 8, 10, 12].

2. Step 2: Select every second element starting from index 1 of the slice

   Indexes inside the slice are 0 to 4. Selecting odd indexes (1, 3) gives elements 6 and 10.

3. Step 3: Check options for correct syntax and output

   arr[1..5].values_at(*arr[1..5].each_index.select(&:odd?)) uses values_at with odd indexes on the slice correctly, returning [6, 10].

4. Final Answer:

   arr[1..5].values_at(*arr[1..5].each_index.select(&:odd?)) -> Option D

5. Quick Check:

   Use values_at with odd indexes on slice for every second element [OK]

Hint: Use values_at with selected indexes for custom slicing [OK]

Common Mistakes:

• Confusing odd/even indexes inside the slice
• Using select without values_at returns elements, not indexes
• Using wrong range operator causing off-by-one errors