What if you could browse a huge sorted list without ever starting over or getting lost?
Why BST Iterator Design in DSA Python?
Imagine you have a huge family tree drawn on paper, and you want to find all family members in order from youngest to oldest. You try to look at each person one by one manually, flipping pages back and forth.
Manually searching through the tree is slow and confusing. You might miss some members or look at the same person multiple times. It's hard to remember where you left off, and you waste time flipping pages.
A BST Iterator acts like a smart bookmark that remembers exactly where you are in the tree. It lets you move step-by-step through the family members in order without losing your place or searching the whole tree every time.
def inorder_traversal(root): if root: inorder_traversal(root.left) print(root.val) inorder_traversal(root.right) # To get next element, you must restart traversal every time.
class BSTIterator: def __init__(self, root): self.stack = [] self._push_left(root) def _push_left(self, node): while node: self.stack.append(node) node = node.left def next(self): node = self.stack.pop() self._push_left(node.right) return node.val def hasNext(self): return len(self.stack) > 0
It enables efficient, step-by-step access to sorted elements in a tree without repeating work or losing track.
Like flipping through a photo album one picture at a time without losing your place, even if the album is very large.
Manual tree traversal is slow and forgetful.
BST Iterator remembers your place and moves forward efficiently.
It makes accessing sorted data easy and fast.
Practice
BST Iterator in a binary search tree?Solution
Step 1: Understand BST Iterator functionality
A BST Iterator is designed to traverse the tree in sorted order, typically ascending, without using recursion.Step 2: Identify the main purpose
It provides a way to get the next smallest element efficiently, which matches To traverse the BST in ascending order without recursion.Final Answer:
To traverse the BST in ascending order without recursion -> Option CQuick Check:
BST Iterator = In-order traversal without recursion [OK]
- Confusing iterator with insertion or deletion
- Thinking it balances the tree automatically
- Assuming it uses recursion internally
Solution
Step 1: Identify the correct data structure for stack
In Python, a stack is commonly implemented using a list, which supports push and pop operations.Step 2: Match the syntax
An empty list is created with[], sostack = []is correct.Final Answer:
stack = [] -> Option AQuick Check:
Stack uses list [] in Python [OK]
- Using {} which creates a dictionary, not a stack
- Using () which creates a tuple, immutable
- Using set() which is unordered
class TreeNode:
def __init__(self, val=0, left=None, right=None):
self.val = val
self.left = left
self.right = right
class BSTIterator:
def __init__(self, root):
self.stack = []
self._push_left(root)
def _push_left(self, node):
while node:
self.stack.append(node)
node = node.left
def next(self):
node = self.stack.pop()
self._push_left(node.right)
return node.val
root = TreeNode(2, TreeNode(1), TreeNode(3))
iterator = BSTIterator(root)
print(iterator.next())
print(iterator.next())
print(iterator.next())Solution
Step 1: Understand the BST structure and iterator initialization
The BST has root 2, left child 1, right child 3. The iterator pushes all left nodes starting from root, so stack = [2,1].Step 2: Trace the next() calls
First next(): pop 1, push left of 1's right (None), output 1.
Second next(): pop 2, push left of 2's right (3), stack = [3], output 2.
Third next(): pop 3, push left of 3's right (None), output 3.Final Answer:
1 2 3 -> Option BQuick Check:
In-order traversal = 1, 2, 3 [OK]
- Confusing order of popping from stack
- Not pushing left children of right subtree
- Assuming preorder or postorder traversal
class BSTIterator:
def __init__(self, root):
self.stack = []
self._push_left(root)
def _push_left(self, node):
while node:
self.stack.append(node)
node = node.right # Bug here
def next(self):
node = self.stack.pop()
self._push_left(node.right)
return node.valSolution
Step 1: Analyze the _push_left method
The method is supposed to push all left children to the stack to simulate in-order traversal, but it incorrectly moves to the right child in the loop.Step 2: Identify the correct traversal direction
It should move to the left child (node = node.left) to push left nodes, so In _push_left, should traverse left child, not right child is correct.Final Answer:
In _push_left, should traverse left child, not right child -> Option AQuick Check:
_push_left must go left, not right [OK]
- Confusing left and right child traversal
- Using set instead of list for stack
- Returning wrong attribute from node
hasNext() and next() methods. Which approach best balances time and space complexity for large BSTs?Solution
Step 1: Evaluate storing all nodes upfront
Storing all nodes in a list uses O(n) space and time upfront, which is inefficient for large trees.Step 2: Consider stack-based on-demand traversal
Using a stack to push left nodes only when needed uses O(h) space (h = tree height) and provides efficient next() calls.Step 3: Analyze recursion and root-only traversal
Recursion each next() call is inefficient and root-only traversal repeats work, both are poor choices.Final Answer:
Use a stack to push left nodes on demand during iteration -> Option DQuick Check:
Stack-based lazy traversal balances time and space [OK]
- Preloading entire tree wastes memory
- Using recursion repeatedly causes overhead
- Restarting traversal from root wastes time
Ready to prove it?
Pass the test and this pattern moves unknown
