Merge Two Sorted Linked Lists in DSA C - Time & Space Complexity

Time Complexity: Merge Two Sorted Linked Lists

O(n)

Understanding Time Complexity

We want to know how the time needed to merge two sorted linked lists changes as the lists get bigger.

Specifically, how does the number of steps grow when the input lists grow?

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

struct ListNode {
    int val;
    struct ListNode *next;
};

struct ListNode* mergeTwoLists(struct ListNode* l1, struct ListNode* l2) {
    if (!l1) return l2;
    if (!l2) return l1;
    if (l1->val < l2->val) {
        l1->next = mergeTwoLists(l1->next, l2);
        return l1;
    } else {
        l2->next = mergeTwoLists(l1, l2->next);
        return l2;
    }
}
    

This code merges two sorted linked lists by comparing their nodes and building a new sorted list.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Comparing nodes from both lists and moving forward one node at a time.
• How many times: Each node from both lists is visited exactly once during the merge.

How Execution Grows With Input

As the total number of nodes in both lists grows, the number of comparisons grows roughly the same amount.

Input Size (n = total nodes)	Approx. Operations
10	About 10 comparisons
100	About 100 comparisons
1000	About 1000 comparisons

Pattern observation: The number of steps grows linearly with the total number of nodes.

Final Time Complexity

Time Complexity: O(n)

This means the time to merge grows directly in proportion to the total number of nodes in both lists.

Common Mistake

[X] Wrong: "The merge takes quadratic time because it compares nodes multiple times."

[OK] Correct: Each node is visited only once, so comparisons happen once per node, not repeatedly.

Interview Connect

Understanding this linear time merge is a key skill for working with linked lists and sorting algorithms.

Self-Check

"What if the input lists were not sorted? How would the time complexity of merging change?"

Practice

1. What is the main goal when merging two sorted linked lists?

easy

A. To create a new sorted linked list containing all elements from both lists

B. To reverse both linked lists

C. To find the maximum element in both lists

D. To delete duplicate elements from both lists

Solution

1. Step 1: Understand the merge operation

   Merging two sorted linked lists means combining their elements into one list that remains sorted.

2. Step 2: Identify the goal

   The goal is to create a new sorted linked list that contains all elements from both input lists in order.

3. Final Answer:

   To create a new sorted linked list containing all elements from both lists -> Option A

4. Quick Check:

   Merge = combine sorted lists [OK]

Hint: Merging means combining sorted lists into one sorted list [OK]

Common Mistakes:

• Thinking merge reverses lists
• Confusing merge with finding max element
• Assuming merge removes duplicates

2. Which of the following is the correct way to declare a node structure for a singly linked list in C?

easy

A. struct Node { int data; struct Node* next; };

B. struct Node { int data; Node* next; };

C. struct Node { int data; struct Node next; };

D. struct Node { int data; struct Node* prev; };

Solution

1. Step 1: Check struct syntax for linked list node

   In C, a node contains data and a pointer to the next node. The pointer must be declared as 'struct Node* next;'.

2. Step 2: Identify correct declaration

   struct Node { int data; struct Node* next; }; correctly declares 'struct Node' with 'int data' and 'struct Node* next;'. struct Node { int data; Node* next; }; misses 'struct' keyword before Node*, struct Node { int data; struct Node next; }; incorrectly uses 'struct Node next;' (not a pointer), and struct Node { int data; struct Node* prev; }; uses 'prev' which is for doubly linked lists.

3. Final Answer:

   struct Node { int data; struct Node* next; }; -> Option A

4. Quick Check:

   Node struct needs pointer to next node [OK]

Hint: Node pointer must use 'struct Node*' in C [OK]

Common Mistakes:

• Omitting 'struct' keyword before Node*
• Using node instead of pointer for next
• Confusing singly linked list with doubly linked list

3. What will be the output linked list after merging these two sorted linked lists?

List1: 1 -> 3 -> 5 -> NULL
List2: 2 -> 4 -> 6 -> NULL

Assuming the merge function merges correctly.

medium

A. 1 -> 3 -> 5 -> 2 -> 4 -> 6 -> NULL

B. 2 -> 4 -> 6 -> 1 -> 3 -> 5 -> NULL

C. 1 -> 2 -> 3 -> 4 -> 5 -> 6 -> NULL

D. 6 -> 5 -> 4 -> 3 -> 2 -> 1 -> NULL

Solution

1. Step 1: Compare elements from both lists in order

   Start with heads: 1 (List1) and 2 (List2). 1 < 2, so 1 goes first. Then compare 3 and 2, 2 < 3, so 2 goes next. Continue this way to merge in sorted order.

2. Step 2: Build merged list step-by-step

   Merged list: 1 -> 2 -> 3 -> 4 -> 5 -> 6 -> NULL.

3. Final Answer:

   1 -> 2 -> 3 -> 4 -> 5 -> 6 -> NULL -> Option C

4. Quick Check:

   Merge keeps sorted order [OK]

Hint: Pick smaller node each step to merge sorted lists [OK]

Common Mistakes:

• Appending one list after the other without sorting
• Reversing the order accidentally
• Skipping nodes during merge

4. Consider this buggy merge function snippet in C:

struct Node* merge(struct Node* l1, struct Node* l2) {
    if (!l1) return l2;
    if (!l2) return l1;
    if (l1->data < l2->data) {
        l1->next = merge(l1->next, l2);
        return l1;
    } else {
        l2->next = merge(l1, l2->next);
        return l2;
    }
}

What is the main issue if this function is called with two sorted lists?

medium

A. It reverses the merged list

B. It merges lists correctly without issues

C. It loses nodes when one list is empty

D. It causes infinite recursion when lists have equal elements

Solution

1. Step 1: Analyze base cases

   If one list is empty (!l1 or !l2), it correctly returns the other list.

2. Step 2: Analyze recursive case

   If l1->data < l2->data, it sets l1->next to the merge of the rest and returns l1. Otherwise, sets l2->next to merge(l1, l2->next) and returns l2. However, when l1->data == l2->data, the else branch is taken repeatedly without advancing l1, causing infinite recursion.

3. Final Answer:

   It causes infinite recursion when lists have equal elements -> Option D

4. Quick Check:

   Equal elements cause infinite recursion due to no advancement in l1 [OK]

Hint: Recursive merge must handle equal elements to avoid infinite recursion [OK]

Common Mistakes:

• Thinking equal elements cause infinite recursion
• Believing it loses nodes on empty lists
• Assuming it reverses the list

5. You have two sorted linked lists:
List1: 1 -> 4 -> 7 -> NULL
List2: 2 -> 4 -> 6 -> 8 -> NULL

Write the merged sorted linked list after merging them and removing duplicate values.

hard

A. 1 -> 4 -> 7 -> 2 -> 4 -> 6 -> 8 -> NULL

B. 1 -> 2 -> 4 -> 6 -> 7 -> 8 -> NULL

C. 1 -> 2 -> 4 -> 4 -> 6 -> 7 -> 8 -> NULL

D. 1 -> 2 -> 6 -> 7 -> 8 -> NULL

Solution

1. Step 1: Merge lists in sorted order

   Merge elements: 1, 2, 4, 4, 6, 7, 8.

2. Step 2: Remove duplicate values

   Remove one of the duplicate 4's to get: 1 -> 2 -> 4 -> 6 -> 7 -> 8 -> NULL.

3. Final Answer:

   1 -> 2 -> 4 -> 6 -> 7 -> 8 -> NULL -> Option B

4. Quick Check:

   Merge + remove duplicates = sorted unique list [OK]

Hint: Merge then skip duplicates for unique sorted list [OK]

Common Mistakes:

• Leaving duplicates in merged list
• Appending lists without sorting
• Removing unique elements by mistake