What if you could find any number in a giant grid without checking every single cell?
Why Search in 2D Matrix in DSA Rust?
Imagine you have a large spreadsheet with rows and columns filled with numbers. You want to find if a specific number exists in this sheet.
Without any method, you start checking each cell one by one from the top-left to the bottom-right.
Checking every cell manually is slow and tiring, especially if the sheet is huge.
You might miss some cells or lose track, making errors easy.
This wastes time and effort.
Using a smart search method for the 2D matrix helps you find the number quickly without checking every cell.
This method uses the order in rows and columns to skip many cells at once.
for row in 0..rows { for col in 0..cols { if matrix[row][col] == target { return true; } } } return false;
let mut row = 0; let mut col = cols as i32 - 1; while row < rows && col >= 0 { if matrix[row][col as usize] == target { return true; } else if matrix[row][col as usize] > target { col -= 1; } else { row += 1; } } return false;
This lets you find any number in a sorted 2D matrix quickly and confidently, saving time and effort.
Think of looking for a name in a phone book sorted by last name and first name. Instead of reading every name, you jump sections to find it fast.
Manual search checks every cell, which is slow.
Smart search uses matrix order to skip cells.
Result: faster, easier, and less error-prone search.
Practice
Solution
Step 1: Understand matrix sorting property
Each row is sorted and the first element of a row is greater than the last element of the previous row, so the entire matrix can be seen as a sorted list.Step 2: Apply binary search on the flattened matrix
We can treat the matrix as a single sorted list and use binary search to find the target efficiently.Final Answer:
Use binary search treating the matrix as a flattened sorted list -> Option AQuick Check:
Matrix sorted row-wise + binary search = Use binary search treating the matrix as a flattened sorted list [OK]
- Searching each row or column linearly wastes time
- Using hash map wastes extra space
- Ignoring the matrix's sorted property
Solution
Step 1: Avoid overflow in mid calculation
Using `(start + end) / 2` can overflow if start and end are large. The safer way is `start + (end - start) / 2`.Step 2: Check other options
let mid = (start - end) / 2; subtracts incorrectly, and D multiplies which is wrong for mid calculation.Final Answer:
let mid = start + (end - start) / 2; -> Option BQuick Check:
Safe mid calculation = let mid = start + (end - start) / 2; [OK]
- Using (start + end) / 2 causing overflow
- Using subtraction incorrectly for mid
- Multiplying indices instead of averaging
let matrix = vec![
vec![1, 3, 5, 7],
vec![10, 11, 16, 20],
vec![23, 30, 34, 60]
];
let target = 5;
let rows = matrix.len();
let cols = matrix[0].len();
let mut start = 0;
let mut end = rows * cols - 1;
let mut found = false;
while start <= end {
let mid = start + (end - start) / 2;
let r = mid / cols;
let c = mid % cols;
if matrix[r][c] == target {
found = true;
break;
} else if matrix[r][c] < target {
start = mid + 1;
} else {
end = mid - 1;
}
}
println!("{}", found);Solution
Step 1: Understand binary search on matrix
The code treats the matrix as a sorted list and uses binary search to find target 5.Step 2: Trace the search for target 5
5 is at matrix[0][2]. The binary search will find it and set found = true.Final Answer:
true -> Option DQuick Check:
Target 5 found = true [OK]
- Confusing row and column calculation
- Off-by-one errors in indices
- Not updating start or end correctly
let matrix = vec![
vec![1, 4, 7, 11],
vec![15, 20, 25, 30],
vec![35, 40, 45, 50]
];
let target = 20;
let rows = matrix.len();
let cols = matrix[0].len();
let mut start = 0;
let mut end = rows * cols;
while start <= end {
let mid = start + (end - start) / 2;
let r = mid / cols;
let c = mid % cols;
if matrix[r][c] == target {
println!("Found");
break;
} else if matrix[r][c] < target {
start = mid + 1;
} else {
end = mid - 1;
}
}Solution
Step 1: Check the range of end index
Matrix has rows * cols elements, so last index is rows * cols - 1, not rows * cols.Step 2: Fix end initialization
Set end = rows * cols - 1 to avoid out-of-bound access when mid equals rows * cols.Final Answer:
end should be rows * cols - 1 instead of rows * cols -> Option AQuick Check:
Index range off-by-one fixed = end should be rows * cols - 1 instead of rows * cols [OK]
- Setting end to rows * cols causing panic
- Swapping row and column calculations
- Incorrect loop condition
Solution
Step 1: Understand matrix property
Rows are sorted but no guarantee that first element of a row is greater than last of previous row, so flattened binary search won't work.Step 2: Use stair-step search from top-right
Starting at top-right, move left if current > target, move down if current < target, efficiently narrowing search.Final Answer:
Start from top-right corner and move left or down based on comparison -> Option CQuick Check:
Stair-step search fits matrix property = Start from top-right corner and move left or down based on comparison [OK]
- Assuming full matrix sorted for binary search
- Searching each row fully wasting time
- Using extra space unnecessarily
Ready to prove it?
Pass the test and this pattern moves unknown
