What if you could remove the first item from a chain instantly without breaking anything?
Why Delete from Beginning of Doubly Linked List in DSA C++?
Imagine you have a long chain of paper clips linked together. You want to remove the first paper clip quickly without breaking the whole chain.
If you try to remove the first paper clip by searching through the entire chain every time, it will take a lot of time and you might accidentally break the chain or lose track of the links.
Using a doubly linked list lets you remove the first item easily by just changing a few links, without touching the rest of the chain. This keeps the chain intact and saves time.
for (Node* current = head; current != nullptr; current = current->next) { if (current == head) { // remove head manually } }
void deleteFromBeginning() {
if (head == nullptr) return;
Node* nodeToDelete = head;
head = head->next;
if (head != nullptr) head->prev = nullptr;
delete nodeToDelete;
}This operation makes it possible to efficiently manage and update sequences where the first element changes often, like task queues or undo histories.
Think of a playlist where the first song finishes and is removed automatically so the next song can start playing without delay.
Manually removing the first element is slow and risky.
Doubly linked lists let you remove the first element quickly by adjusting just a few pointers.
This keeps the list intact and operations efficient.
Practice
head pointer when you delete the first node from a doubly linked list?Solution
Step 1: Understand the head pointer role
Theheadpoints to the first node in the doubly linked list.Step 2: After deletion, update the head pointer
When the first node is deleted, theheadmust point to the next node, which becomes the new first node.Final Answer:
It moves to the second node in the list -> Option CQuick Check:
Head points to new first node after deletion [OK]
- Not updating head pointer after deletion
- Setting head to null without checking list size
- Leaving head pointing to deleted node
Solution
Step 1: Store current head in temp
We save the current first node in a temporary pointer to delete it safely after updating head.Step 2: Update head and fix previous pointer
Setheadto the next node, then sethead->prevtonullptrto detach the old first node.Step 3: Delete the old first node
Finally, delete the node stored intempto free memory.Final Answer:
Node* temp = head; head = head->next; head->prev = nullptr; delete temp; -> Option BQuick Check:
Proper order: save, update, fix pointers, delete [OK]
- Deleting head before updating pointers
- Not setting head->prev to nullptr
- Accessing head->prev when head is nullptr
struct Node {
int data;
Node* prev;
Node* next;
};
Node* head = new Node{1, nullptr, nullptr};
Node* second = new Node{2, head, nullptr};
head->next = second;
// Delete from beginning
Node* temp = head;
head = head->next;
head->prev = nullptr;
delete temp;
// Print list
Node* curr = head;
while(curr != nullptr) {
std::cout << curr->data << " ";
curr = curr->next;
}Solution
Step 1: Initial list setup
List has two nodes: 1 (head) -> 2. Head points to node with data 1.Step 2: Delete first node and update pointers
Head moves to second node (data 2), and itsprevis set tonullptr. The first node is deleted.Step 3: Print remaining list
Only node with data 2 remains, so output is "2".Final Answer:
2 -> Option DQuick Check:
After deletion, list starts at 2 [OK]
- Printing deleted node's data
- Not updating head->prev to nullptr
- Assuming both nodes print after deletion
void deleteBeginning(Node*& head) {
if (head == nullptr) return;
delete head;
head = head->next;
if (head != nullptr) head->prev = nullptr;
}Solution
Step 1: Analyze deletion order
The code deletesheadfirst, then tries to accesshead->next, which is invalid after deletion.Step 2: Correct order to avoid undefined behavior
First savehead->nextin a temp pointer, updatehead, then delete old node.Final Answer:
Deleting head before updating head pointer causes undefined behavior -> Option AQuick Check:
Accessing deleted memory causes error [OK]
- Deleting node before updating pointers
- Accessing deleted node's members
- Not checking for empty list
Solution
Step 1: Initial list nodes
List is 10 <-> 20 <-> 30 <-> 40, head points to 10.Step 2: First deletion
Delete node 10, head moves to 20, set head->prev = nullptr. List now: 20 <-> 30 <-> 40.Step 3: Second deletion
Delete node 20, head moves to 30, set head->prev = nullptr. List now: 30 <-> 40.Final Answer:
30 <-> 40 -> Option AQuick Check:
Two deletions remove first two nodes [OK]
- Deleting only once instead of twice
- Not updating head->prev after second deletion
- Printing old list without deletions
Ready to prove it?
Pass the test and this pattern moves unknown
