Convert Sorted Array to Balanced BST in DSA Go - Time & Space Complexity
We want to understand how the time needed to build a balanced binary search tree changes as the input array grows.
Specifically, how does the work increase when we convert a sorted array into a balanced BST?
Analyze the time complexity of the following code snippet.
func sortedArrayToBST(nums []int) *TreeNode {
if len(nums) == 0 {
return nil
}
mid := len(nums) / 2
root := &TreeNode{Val: nums[mid]}
root.Left = sortedArrayToBST(nums[:mid])
root.Right = sortedArrayToBST(nums[mid+1:])
return root
}
This code builds a balanced BST by choosing the middle element as root and recursively doing the same for left and right halves.
Identify the loops, recursion, array traversals that repeat.
- Primary operation: Recursive calls splitting the array and creating nodes.
- How many times: Each element is processed exactly once to create a node.
Each recursive call splits the array roughly in half, and every element is visited once to create a node.
| Input Size (n) | Approx. Operations |
|---|---|
| 10 | About 10 node creations and splits |
| 100 | About 100 node creations and splits |
| 1000 | About 1000 node creations and splits |
Pattern observation: The work grows roughly in direct proportion to the input size.
Time Complexity: O(n)
This means the time to build the tree grows linearly with the number of elements in the array.
[X] Wrong: "Because the function calls itself twice, the time complexity is exponential like O(2^n)."
[OK] Correct: Each element is processed only once, and the array is split, so the total work adds up linearly, not exponentially.
Understanding this helps you explain how recursion and divide-and-conquer work together efficiently to build balanced trees.
"What if we did not pick the middle element but always picked the first element as root? How would the time complexity change?"
Practice
Solution
Step 1: Understand the problem goal
The goal is to build a BST that is balanced, meaning the tree height is minimized to allow fast searching.Step 2: Why minimal height matters
A balanced BST ensures operations like search, insert, and delete run in O(log n) time, which is efficient.Final Answer:
To create a BST with minimal height for efficient search -> Option AQuick Check:
Balanced BST = minimal height = efficient search [OK]
- Confusing BST with linked list
- Thinking sorting again is needed
- Ignoring tree balance importance
Solution
Step 1: Identify input and output types
The function takes a slice of integers (sorted array) and returns a pointer to the root TreeNode of the BST.Step 2: Match correct Go syntax
func sortedArrayToBST(nums []int) *TreeNode matches: input is []int, output is *TreeNode pointer, which is standard for tree nodes in Go.Final Answer:
func sortedArrayToBST(nums []int) *TreeNode -> Option AQuick Check:
Input []int, output *TreeNode pointer [OK]
- Using int instead of slice for input
- Returning int or slice instead of TreeNode pointer
- Missing pointer in return type
[1, 2, 3, 4, 5], what is the root value of the balanced BST created by the standard algorithm?Solution
Step 1: Find middle element of array
The middle index of [1, 2, 3, 4, 5] is 2 (0-based), so middle element is 3.Step 2: Root is middle element
The root of the balanced BST is the middle element to balance left and right subtrees.Final Answer:
3 -> Option CQuick Check:
Middle element = root = 3 [OK]
- Choosing first or last element as root
- Off-by-one error in middle index
- Confusing index with value
func sortedArrayToBST(nums []int) *TreeNode {
if len(nums) == 0 {
return nil
}
mid := len(nums) / 2
root := &TreeNode{Val: nums[mid]}
root.Left = sortedArrayToBST(nums[:mid])
root.Right = sortedArrayToBST(nums[mid:])
return root
}
What is the bug in this code?Solution
Step 1: Analyze slicing for right subtree
The right subtree slice uses nums[mid:], which includes the middle element again, causing duplicate nodes.Step 2: Correct slice to exclude middle element
Right subtree should start from mid+1 to avoid including root again.Final Answer:
The right subtree slice should start from mid+1, not mid -> Option DQuick Check:
Right slice = nums[mid+1:] to avoid duplicates [OK]
- Using mid instead of mid+1 for right slice
- Wrong base case condition
- Returning wrong type
[10, 20, 30, 40, 50, 60, 70]. After converting it to a balanced BST, what is the inorder traversal of the BST?Solution
Step 1: Understand inorder traversal of BST
Inorder traversal visits nodes in ascending order for BST, so it returns the sorted array.Step 2: Confirm traversal matches original array
Since the BST is built from sorted array, inorder traversal outputs the same sorted sequence.Final Answer:
[10, 20, 30, 40, 50, 60, 70] -> Option BQuick Check:
Inorder traversal = sorted array [OK]
- Confusing preorder or postorder with inorder
- Assuming traversal changes order
- Mixing up traversal outputs
Ready to prove it?
Pass the test and this pattern moves unknown
