Overflow in intermediate arithmetic
Wrong move: Temporary multiplications exceed integer bounds.
Usually fails on: Large inputs wrap around unexpectedly.
Fix: Use wider types, modular arithmetic, or rearranged operations.
Build confidence with an intuition-first walkthrough focused on math fundamentals.
An axis-aligned rectangle is represented as a list [x1, y1, x2, y2], where (x1, y1) is the coordinate of its bottom-left corner, and (x2, y2) is the coordinate of its top-right corner. Its top and bottom edges are parallel to the X-axis, and its left and right edges are parallel to the Y-axis.
Two rectangles overlap if the area of their intersection is positive. To be clear, two rectangles that only touch at the corner or edges do not overlap.
Given two axis-aligned rectangles rec1 and rec2, return true if they overlap, otherwise return false.
Example 1:
Input: rec1 = [0,0,2,2], rec2 = [1,1,3,3] Output: true
Example 2:
Input: rec1 = [0,0,1,1], rec2 = [1,0,2,1] Output: false
Example 3:
Input: rec1 = [0,0,1,1], rec2 = [2,2,3,3] Output: false
Constraints:
rec1.length == 4rec2.length == 4-109 <= rec1[i], rec2[i] <= 109rec1 and rec2 represent a valid rectangle with a non-zero area.Problem summary: An axis-aligned rectangle is represented as a list [x1, y1, x2, y2], where (x1, y1) is the coordinate of its bottom-left corner, and (x2, y2) is the coordinate of its top-right corner. Its top and bottom edges are parallel to the X-axis, and its left and right edges are parallel to the Y-axis. Two rectangles overlap if the area of their intersection is positive. To be clear, two rectangles that only touch at the corner or edges do not overlap. Given two axis-aligned rectangles rec1 and rec2, return true if they overlap, otherwise return false.
Start with the most direct exhaustive search. That gives a correctness anchor before optimizing.
Pattern signal: Math
[0,0,2,2] [1,1,3,3]
[0,0,1,1] [1,0,2,1]
[0,0,1,1] [2,2,3,3]
rectangle-area)Source-backed implementations are provided below for direct study and interview prep.
// Accepted solution for LeetCode #836: Rectangle Overlap
class Solution {
public boolean isRectangleOverlap(int[] rec1, int[] rec2) {
int x1 = rec1[0], y1 = rec1[1], x2 = rec1[2], y2 = rec1[3];
int x3 = rec2[0], y3 = rec2[1], x4 = rec2[2], y4 = rec2[3];
return !(y3 >= y2 || y4 <= y1 || x3 >= x2 || x4 <= x1);
}
}
// Accepted solution for LeetCode #836: Rectangle Overlap
func isRectangleOverlap(rec1 []int, rec2 []int) bool {
x1, y1, x2, y2 := rec1[0], rec1[1], rec1[2], rec1[3]
x3, y3, x4, y4 := rec2[0], rec2[1], rec2[2], rec2[3]
return !(y3 >= y2 || y4 <= y1 || x3 >= x2 || x4 <= x1)
}
# Accepted solution for LeetCode #836: Rectangle Overlap
class Solution:
def isRectangleOverlap(self, rec1: List[int], rec2: List[int]) -> bool:
x1, y1, x2, y2 = rec1
x3, y3, x4, y4 = rec2
return not (y3 >= y2 or y4 <= y1 or x3 >= x2 or x4 <= x1)
// Accepted solution for LeetCode #836: Rectangle Overlap
struct Solution;
impl Solution {
fn is_rectangle_overlap(rec1: Vec<i32>, rec2: Vec<i32>) -> bool {
rec1[2] > rec2[0] && rec1[0] < rec2[2] && rec1[1] < rec2[3] && rec1[3] > rec2[1]
}
}
#[test]
fn test() {
let rec1 = vec![0, 0, 2, 2];
let rec2 = vec![1, 1, 3, 3];
assert_eq!(Solution::is_rectangle_overlap(rec1, rec2), true);
let rec1 = vec![0, 0, 1, 1];
let rec2 = vec![1, 0, 2, 1];
assert_eq!(Solution::is_rectangle_overlap(rec1, rec2), false);
}
// Accepted solution for LeetCode #836: Rectangle Overlap
function isRectangleOverlap(rec1: number[], rec2: number[]): boolean {
const [x1, y1, x2, y2] = rec1;
const [x3, y3, x4, y4] = rec2;
return !(y3 >= y2 || y4 <= y1 || x3 >= x2 || x4 <= x1);
}
Use this to step through a reusable interview workflow for this problem.
Simulate the process step by step — multiply n times, check each number up to n, or iterate through all possibilities. Each step is O(1), but doing it n times gives O(n). No extra space needed since we just track running state.
Math problems often have a closed-form or O(log n) solution hidden behind an O(n) simulation. Modular arithmetic, fast exponentiation (repeated squaring), GCD (Euclidean algorithm), and number theory properties can dramatically reduce complexity.
Review these before coding to avoid predictable interview regressions.
Wrong move: Temporary multiplications exceed integer bounds.
Usually fails on: Large inputs wrap around unexpectedly.
Fix: Use wider types, modular arithmetic, or rearranged operations.