Why Reverse a Singly Linked List Recursive in DSA C++?

The Big Idea

What if you could flip a long chain perfectly by just trusting the power of recursion?

The Scenario

Imagine you have a long chain of paper clips linked one after another. You want to flip the entire chain so the last clip becomes the first and the first becomes the last.

Doing this by hand means unhooking each clip and reattaching it in reverse order, which is slow and tricky.

The Problem

Manually reversing the chain clip by clip is slow and easy to mess up. You might lose track of which clip connects to which, or accidentally break the chain.

Doing this with code using loops can get complicated and hard to read, especially if the chain is very long.

The Solution

Using recursion to reverse the chain means you let the computer handle flipping each link step by step, starting from the end and working back to the start.

This method is clean, easy to understand, and reduces the chance of mistakes.

Before vs After

✗ Before

Node* reverseList(Node* head) {
  Node* previous = nullptr;
  Node* current = head;
  while (current != nullptr) {
    Node* next = current->next;
    current->next = previous;
    previous = current;
    current = next;
  }
  return previous;
}

✓ After

Node* reverseList(Node* head) {
  if (head == nullptr || head->next == nullptr) {
    return head;
  }
  Node* newHead = reverseList(head->next);
  head->next->next = head;
  head->next = nullptr;
  return newHead;
}

What It Enables

This lets you easily flip linked lists of any size with simple, elegant code that reads like a story.

Real Life Example

Think of undoing a stack of papers one by one, but instead of pulling from the top, you magically flip the entire stack so the last paper is now on top.

Key Takeaways

Manual reversal is slow and error-prone.

Recursive reversal breaks the problem into smaller, easier steps.

Recursive code is cleaner and easier to understand for reversing linked lists.

Practice

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

easy

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

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

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

D. Create a new list and copy elements in reverse order

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 should point back to current node, then current node points to null.

3. Final Answer:

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

4. Quick Check:

   Recursive reversal = Reverse rest first [OK]

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

Common Mistakes:

• Trying to swap data instead of pointers
• Not setting current node's next to null
• Confusing iterative and recursive methods

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

easy

A. if (head->next == nullptr) return head;

B. if (head == nullptr || head->next == nullptr) return head;

C. if (head == nullptr) return nullptr;

D. if (head->next == nullptr) head = nullptr;

Solution

1. Step 1: Identify base cases for recursion

   Base case should handle empty list and single node list, both are already reversed.

2. Step 2: Choose condition covering both cases

   Condition 'head == nullptr || head->next == nullptr' returns head for empty or single node list.

3. Final Answer:

   if (head == nullptr || head->next == nullptr) return head; -> Option B

4. Quick Check:

   Base case = empty or single node [OK]

Hint: Base case covers empty or single node list [OK]

Common Mistakes:

• Returning nullptr for single node list
• Not handling empty list
• Incorrectly modifying head in base case

3. Given the following linked list: 1 -> 2 -> 3 -> null, what will be the printed output after applying this recursive reverse function?

Node* reverse(Node* head) {
  if (!head || !head->next) return head;
  Node* newHead = reverse(head->next);
  head->next->next = head;
  head->next = nullptr;
  return newHead;
}

medium

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

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

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

D. 3 -> 2 -> 1 -> 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: Reverse pointers on return

   On unwind from reverse(3), in reverse(2): head(2)->next(3)->next = 2 so 3->next=2, then 2->next=nullptr. Then in reverse(1): 2->next=1, 1->next=nullptr.

3. Final Answer:

   3 -> 2 -> 1 -> null -> Option D

4. Quick Check:

   Reversed list = 3->2->1 [OK]

Hint: Follow recursion unwind to see pointer reversal [OK]

Common Mistakes:

• Not setting head->next to nullptr causing cycle
• Confusing node values order
• Returning wrong node as new head

4. Identify the bug in this recursive reverse function and select the correct fix:

Node* reverse(Node* head) {
  if (!head || !head->next) return head;
  Node* newHead = reverse(head->next);
  head->next->next = head;
  return newHead;
}

medium

A. Remove the recursive call and use iteration

B. Change base case to 'if (head->next == nullptr) return head;'

C. Add 'head->next = nullptr;' before returning newHead

D. Return 'head' instead of 'newHead'

Solution

1. Step 1: Analyze missing pointer update

   Function misses setting 'head->next = nullptr', causing cycle in reversed list.

2. Step 2: Fix by setting 'head->next = nullptr'

   Adding 'head->next = nullptr;' breaks old link, preventing cycle and correctly terminates list.

3. Final Answer:

   Add 'head->next = nullptr;' before returning newHead -> Option C

4. Quick Check:

   Break old next link to avoid cycle [OK]

Hint: Always set current node's next to nullptr after reversing [OK]

Common Mistakes:

• Forgetting to break old next pointer
• Incorrect base case causing null pointer dereference
• Returning wrong node as new head

5. You want to reverse a singly linked list recursively but also count how many nodes were reversed. Which modification correctly adds counting without breaking the reversal?

Node* reverseCount(Node* head, int &count) {
  if (!head || !head->next) {
    count++;
    return head;
  }
  Node* newHead = reverseCount(head->next, count);
  head->next->next = head;
  head->next = nullptr;
  count++;
  return newHead;
}

What will be the value of count after reversing a list with 4 nodes?

hard

A. 4

B. 3

C. 5

D. 0

Solution

1. Step 1: Understand counting in base case

   When recursion reaches last node, count increments by 1 for that node.

2. Step 2: Count increments on each return step

   Each return from recursion increments count by 1 for each node processed, total nodes counted equals list length.

3. Final Answer:

   4 -> Option A

4. Quick Check:

   Count increments once per node [OK]

Hint: Increment count once per node during recursion [OK]

Common Mistakes:

• Counting only in base case missing other nodes
• Incrementing count twice per node
• Not passing count by reference