Delete a Node from Circular Linked List in DSA Rust - Time & Space Complexity

Time Complexity: Delete a Node from Circular Linked List

O(n)

Understanding Time Complexity

When deleting a node from a circular linked list, we want to know how the time needed changes as the list grows.

We ask: How many steps does it take to find and remove the node?

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

fn delete_node(head: &mut Option>, key: i32) {
    if head.is_none() {
        return;
    }
    let mut curr = head.as_mut().unwrap();
    let mut prev = curr;
    loop {
        if curr.data == key {
            prev.next = curr.next.take();
            break;
        }
        prev = curr;
        curr = curr.next.as_mut().unwrap();
        if std::ptr::eq(curr.as_ref(), head.as_ref().unwrap().as_ref()) {
            break;
        }
    }
}
    

This code searches the circular linked list for a node with the given key and removes it by adjusting links.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Looping through nodes one by one to find the node to delete.
• How many times: Up to n times, where n is the number of nodes in the list.

How Execution Grows With Input

As the list grows, the number of steps to find the node grows roughly the same as the list size.

Input Size (n)	Approx. Operations
10	Up to 10 steps
100	Up to 100 steps
1000	Up to 1000 steps

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

Final Time Complexity

Time Complexity: O(n)

This means the time to delete a node grows directly with the list size because we may need to check each node once.

Common Mistake

[X] Wrong: "Deleting a node in a circular linked list always takes constant time because we just change links."

[OK] Correct: We must first find the node, which can take time proportional to the list size, so it is not always instant.

Interview Connect

Understanding this helps you explain how linked lists work and how searching affects operation speed, a key skill in many coding challenges.

Self-Check

"What if the list was doubly linked? How would the time complexity of deleting a node change?"

Practice

1. What happens when you delete the only node in a circular linked list?

easy

A. The list points to itself indefinitely.

B. The list still contains the deleted node.

C. The list becomes empty (null).

D. The list throws an error.

Solution

1. Step 1: Understand the structure of a single-node circular linked list

   In a circular linked list with one node, the node's next pointer points to itself.

2. Step 2: Delete the only node

   Removing this node means no nodes remain, so the list becomes empty (null).

3. Final Answer:

   The list becomes empty (null). -> Option C

4. Quick Check:

   Single node deleted = empty list [OK]

Hint: Deleting the only node empties the list [OK]

Common Mistakes:

• Assuming the list still contains the deleted node
• Thinking the list points to itself after deletion
• Expecting an error instead of empty list

2. Which Rust syntax correctly declares a mutable circular linked list node struct with a next pointer?

easy

A. struct Node { data: i32, next: Option }

B. struct Node { data: i32, next: &Node }

C. struct Node { data: i32, next: Node }

D. struct Node { data: i32, next: Option> }

Solution

1. Step 1: Understand Rust ownership for circular references

   Rust disallows direct cyclic ownership. Using Rc allows multiple owners and interior mutability.

2. Step 2: Identify correct syntax for mutable circular linked list node

   struct Node { data: i32, next: Option> } uses Option> which supports cycles and mutability safely.

3. Final Answer:

   struct Node { data: i32, next: Option> } -> Option D

4. Quick Check:

   Use Rc for circular mutable nodes [OK]

Hint: Use Rc and RefCell for mutable circular references in Rust [OK]

Common Mistakes:

• Using plain Box<Node> causes ownership errors
• Using references (&Node) disallows ownership
• Using Node directly causes infinite size error

3. Given this Rust code snippet deleting a node with value 3 from a circular linked list:

let mut head = create_circular_list(vec![1, 2, 3, 4]); delete_node(&mut head, 3); print_list(&head);

What is the printed output?

medium

A. 1 -> 2 -> 4 -> 1 (circular)

B. 1 -> 2 -> 3 -> 4 -> 1 (circular)

C. 2 -> 3 -> 4 -> 2 (circular)

D. 1 -> 2 -> 4 -> null

Solution

1. Step 1: Understand the initial list

   The list is circular with nodes 1, 2, 3, 4 linked in a loop.

2. Step 2: Delete node with value 3

   Node 3 is removed, so the list becomes 1 -> 2 -> 4, then back to 1.

3. Final Answer:

   1 -> 2 -> 4 -> 1 (circular) -> Option A

4. Quick Check:

   Deleted 3, list loops 1-2-4 [OK]

Hint: Deleting node removes it, links neighbors circularly [OK]

Common Mistakes:

• Forgetting to link node 2 to node 4
• Printing null instead of circular loop
• Not deleting the correct node

4. Identify the bug in this Rust function snippet for deleting a node from a circular linked list:

fn delete_node(head: &mut Option>, key: i32) { let mut curr = head.clone().unwrap(); while curr.borrow().data != key { curr = curr.borrow().next.clone().unwrap(); } let next_node = curr.borrow().next.clone(); curr.borrow_mut().next = next_node.unwrap().borrow().next.clone(); }

medium

A. It causes infinite loop if key not found.

B. It does not handle deleting the head node correctly.

C. It leaks memory by not freeing nodes.

D. It uses unwrap() unsafely causing panic.

Solution

1. Step 1: Analyze the while loop condition

   The loop continues until curr's data equals key, but no check if key exists, so it loops infinitely if key missing.

2. Step 2: Check for missing exit condition

   Without a break or stop when full circle is done, infinite loop occurs if key not found.

3. Final Answer:

   It causes infinite loop if key not found. -> Option A

4. Quick Check:

   No key check = infinite loop risk [OK]

Hint: Always check for key existence to avoid infinite loops [OK]

Common Mistakes:

• Assuming key always exists
• Not checking for full circle traversal
• Ignoring unwrap() panic risks

5. How would you delete the head node from a circular linked list in Rust while maintaining the circular structure?

hard

A. Replace head data with next node data and delete next node.

B. Find the last node, set its next to head's next, then update head to head's next.

C. Delete head and leave the last node pointing to old head.

D. Set head to None directly without updating other nodes.

Solution

1. Step 1: Locate the last node in the circular list

   The last node points back to head; find it by traversing until next points to head.

2. Step 2: Update last node's next pointer and head

   Set last node's next to head's next node, then update head to head's next to maintain circularity.

3. Final Answer:

   Find last node, link it to head's next, update head to head's next. -> Option B

4. Quick Check:

   Update last node and head to delete head safely [OK]

Hint: Link last node to new head, then update head [OK]

Common Mistakes:

• Setting head to None breaks circularity
• Not updating last node's next pointer
• Deleting head without adjusting links