Reverse a Singly Linked List Recursive in DSA C# - Time & Space Complexity

Time Complexity: Reverse a Singly Linked List Recursive

O(n)

Understanding Time Complexity

We want to understand how the time needed to reverse a linked list using recursion changes as the list grows.

How does the number of steps grow when the list gets longer?

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

public class Node {
    public int Value;
    public Node Next;
    public Node(int val) { Value = val; Next = null; }
}

public Node ReverseRecursive(Node head) {
    if (head == null || head.Next == null) return head;
    Node newHead = ReverseRecursive(head.Next);
    head.Next.Next = head;
    head.Next = null;
    return newHead;
}
    

This code reverses a singly linked list by calling itself on the next node until it reaches the end, then rewires the links backward.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Recursive call on the next node in the list.
• How many times: Once for each node in the list, so n times for a list of size n.

How Execution Grows With Input

Each node causes one recursive call, so the steps grow directly with the number of nodes.

Input Size (n)	Approx. Operations
10	About 10 recursive calls and rewiring steps
100	About 100 recursive calls and rewiring steps
1000	About 1000 recursive calls and rewiring steps

Pattern observation: The number of operations grows linearly as the list size increases.

Final Time Complexity

Time Complexity: O(n)

This means the time to reverse the list grows in direct proportion to the number of nodes.

Common Mistake

[X] Wrong: "Recursive reversal is faster because it uses recursion instead of loops."

[OK] Correct: Both recursion and loops visit each node once, so they take similar time. Recursion adds function call overhead but does not reduce the number of steps.

Interview Connect

Understanding recursive time complexity helps you explain your code clearly and shows you know how your solution scales with input size.

Self-Check

"What if we changed the recursive reversal to an iterative approach? How would the time complexity change?"

Practice

1. What is the main idea behind reversing a singly linked list using recursion?

easy

A. Create a new list and copy nodes in reverse order

B. Swap the values of the first and last nodes only

C. Iterate through the list and reverse pointers in a loop

D. Reverse the rest of the list first, then fix the current node's next pointer

Solution

1. Step 1: Understand recursion on linked list

   Recursion works by solving a smaller part first, here reversing from the next node onward.

2. Step 2: Fix current node's pointer after recursion

   After reversing the rest, the current node's next node points back to it, reversing the link.

3. Final Answer:

   Reverse the rest of the list first, then fix the current node's next pointer -> Option D

4. Quick Check:

   Recursive reversal = reverse rest then fix current [OK]

Hint: Think: reverse smaller list first, then fix current link [OK]

Common Mistakes:

• Trying to swap node values instead of pointers
• Not fixing the current node's next pointer after recursion
• Using iteration instead of recursion

2. Which of the following is the correct base case for a recursive function that reverses a singly linked list?

easy

A. if (head == null) return new Node();

B. if (head.next == null) return null;

C. if (head == null || head.next == null) return head;

D. if (head == null) return head.next;

Solution

1. Step 1: Identify when recursion should stop

   The base case is when the list is empty or has only one node, so no reversal needed.

2. Step 2: Check the correct base case syntax

   Return the head itself if it is null or the last node (head.next == null).

3. Final Answer:

   if (head == null || head.next == null) return head; -> Option C

4. Quick Check:

   Base case = empty or single node returns head [OK]

Hint: Base case: empty or single node returns itself [OK]

Common Mistakes:

• Returning null when list has one node
• Accessing head.next without checking if head is null
• Creating new nodes unnecessarily

3. What will be the output linked list after running this recursive reverse function on the list 1 -> 2 -> 3 -> null?

Node Reverse(Node head) {
  if (head == null || head.next == null) return head;
  Node newHead = Reverse(head.next);
  head.next.next = head;
  head.next = null;
  return newHead;
}

medium

A. 3 -> 2 -> 1 -> null

B. 1 -> 2 -> 3 -> null

C. 2 -> 3 -> 1 -> null

D. 3 -> 1 -> 2 -> null

Solution

1. Step 1: Trace recursion calls

   Reverse(1) calls Reverse(2), which calls Reverse(3). Reverse(3) returns node 3 as base case.

2. Step 2: Fix pointers on return

   head.next.next = head reverses link: 3.next = 2, then 2.next = 1, and 1.next = null.

3. Final Answer:

   3 -> 2 -> 1 -> null -> Option A

4. Quick Check:

   Recursive reversal output = reversed list [OK]

Hint: Follow recursion bottom-up to see pointer reversal [OK]

Common Mistakes:

• Not setting head.next to null causing cycle
• Confusing node values with pointers
• Returning wrong node as new head

4. Identify the error in this recursive reverse function and choose the fix:

Node Reverse(Node head) {
  if (head == null) return null;
  Node newHead = Reverse(head.next);
  head.next.next = head;
  return newHead;
}

medium

A. Should return head instead of newHead

B. Missing base case for single node; add 'head.next == null' check

C. head.next.next = head causes null pointer; fix by checking head.next

D. No error; code is correct

Solution

1. Step 1: Check base case correctness

   Base case only checks head == null, missing single node case (head.next == null).

2. Step 2: Consequence of missing base case

   Without single node base case, head.next may be null causing head.next.next to throw error.

3. Final Answer:

   Missing base case for single node; add 'head.next == null' check -> Option B

4. Quick Check:

   Base case must handle empty and single node [OK]

Hint: Base case must cover empty and single node to avoid errors [OK]

Common Mistakes:

• Ignoring single node base case
• Not setting head.next = null after reversal
• Returning wrong node as new head

5. Given a singly linked list with nodes containing values 10 -> 20 -> 30 -> 40 -> null, what will be the printed output after applying this recursive reverse function?

Node Reverse(Node head) {
  if (head == null || head.next == null) return head;
  Node newHead = Reverse(head.next);
  head.next.next = head;
  head.next = null;
  return newHead;
}

// After reversal, print list from newHead

hard

A. 40 -> 30 -> 20 -> 10 -> null

B. 10 -> 20 -> 30 -> 40 -> null

C. 40 -> 10 -> 20 -> 30 -> null

D. 30 -> 40 -> 20 -> 10 -> null

Solution

1. Step 1: Trace recursive reversal on given list

   Recursion reverses from last node 40 back to 10, fixing pointers step-by-step.

2. Step 2: Confirm final reversed list order

   After reversal, list order is 40 -> 30 -> 20 -> 10 -> null.

3. Final Answer:

   40 -> 30 -> 20 -> 10 -> null -> Option A

4. Quick Check:

   Recursive reversal reverses entire list order [OK]

Hint: Reversal flips list order completely [OK]

Common Mistakes:

• Printing original list instead of reversed
• Forgetting to set head.next = null causing cycle
• Misreading pointer changes as value swaps