Learning Outcome
After this lesson, you should be able to preserve the order of non-zero values while moving zeroes to the end in-place.
Problem Statement
Given an integer array nums, move all zeroes to the end while keeping the relative order of non-zero elements. Modify the array in-place.
| Input | Output | Why |
|---|---|---|
[0, 1, 0, 3, 12] | [1, 3, 12, 0, 0] | Non-zero values keep their original order. |
Brute Force Approach
Create a temporary list of non-zero values, copy them back into the array, and fill the rest with zeroes.
This is clear, but it uses O(n) extra space. The interview usually expects in-place modification.
Optimized Approach
Use write as the position where the next non-zero value should go. Scan the array once. Whenever a non-zero value appears, write it at write and move write forward.
After all non-zero values are compacted at the front, fill the remaining positions with zeroes.
Exact Pseudocode
write = 0
for read from 0 to length(nums) - 1:
if nums[read] != 0:
nums[write] = nums[read]
write = write + 1
while write < length(nums):
nums[write] = 0
write = write + 1
Reference Code
class Solution:
def moveZeroes(self, nums):
write = 0
for value in nums:
if value != 0:
nums[write] = value
write += 1
while write < len(nums):
nums[write] = 0
write += 1Sample Dry Run
| read value | write before | array after action | write after |
|---|---|---|---|
| 0 | 0 | [0, 1, 0, 3, 12] | 0 |
| 1 | 0 | [1, 1, 0, 3, 12] | 1 |
| 0 | 1 | [1, 1, 0, 3, 12] | 1 |
| 3 | 1 | [1, 3, 0, 3, 12] | 2 |
| 12 | 2 | [1, 3, 12, 3, 12] | 3 |
| fill zeroes | 3 | [1, 3, 12, 0, 0] | 5 |
Complexity
| Measure | Value | Reason |
|---|---|---|
| Time | O(n) | The array is scanned once, then the remaining tail is filled. |
| Space | O(1) | The update is in-place. |
Edge Cases
- All zeroes.
- No zeroes.
- Zeroes already at the end.
Interview Checklist
- Preserve order of non-zero values.
- Do not allocate another array unless allowed.
- Remember to fill the tail with zeroes.
FAQs
Why not swap every zero with a later non-zero?
Swapping can still work, but the write-pointer version is easier to reason about and preserves order cleanly.
Why does the first pass overwrite values?
Only the compacted prefix matters after the pass. The remaining tail is overwritten with zeroes.
Is this a two-pointer problem?
Yes. The read pointer scans values and the write pointer marks the next non-zero position.