Off-by-one on range boundaries
Wrong move: Loop endpoints miss first/last candidate.
Usually fails on: Fails on minimal arrays and exact-boundary answers.
Fix: Re-derive loops from inclusive/exclusive ranges before coding.
Build confidence with an intuition-first walkthrough focused on core interview patterns fundamentals.
Given an object or an array, return if it is empty.
You may assume the object or array is the output of JSON.parse.
Example 1:
Input: obj = {"x": 5, "y": 42}
Output: false
Explanation: The object has 2 key-value pairs so it is not empty.
Example 2:
Input: obj = {}
Output: true
Explanation: The object doesn't have any key-value pairs so it is empty.
Example 3:
Input: obj = [null, false, 0] Output: false Explanation: The array has 3 elements so it is not empty.
Constraints:
obj is a valid JSON object or array2 <= JSON.stringify(obj).length <= 105Problem summary: Given an object or an array, return if it is empty. An empty object contains no key-value pairs. An empty array contains no elements. You may assume the object or array is the output of JSON.parse.
Start with the most direct exhaustive search. That gives a correctness anchor before optimizing.
Pattern signal: General problem-solving
{"x": 5, "y": 42}{}[null, false, 0]
Source-backed implementations are provided below for direct study and interview prep.
// Accepted solution for LeetCode #2727: Is Object Empty
// Auto-generated Java example from ts.
class Solution {
public void exampleSolution() {
}
}
// Reference (ts):
// // Accepted solution for LeetCode #2727: Is Object Empty
// function isEmpty(obj: Record<string, any> | any[]): boolean {
// for (const x in obj) {
// return false;
// }
// return true;
// }
// Accepted solution for LeetCode #2727: Is Object Empty
// Auto-generated Go example from ts.
func exampleSolution() {
}
// Reference (ts):
// // Accepted solution for LeetCode #2727: Is Object Empty
// function isEmpty(obj: Record<string, any> | any[]): boolean {
// for (const x in obj) {
// return false;
// }
// return true;
// }
# Accepted solution for LeetCode #2727: Is Object Empty
# Auto-generated Python example from ts.
def example_solution() -> None:
return
# Reference (ts):
# // Accepted solution for LeetCode #2727: Is Object Empty
# function isEmpty(obj: Record<string, any> | any[]): boolean {
# for (const x in obj) {
# return false;
# }
# return true;
# }
// Accepted solution for LeetCode #2727: Is Object Empty
// Rust example auto-generated from ts reference.
// Replace the signature and local types with the exact LeetCode harness for this problem.
impl Solution {
pub fn rust_example() {
// Port the logic from the reference block below.
}
}
// Reference (ts):
// // Accepted solution for LeetCode #2727: Is Object Empty
// function isEmpty(obj: Record<string, any> | any[]): boolean {
// for (const x in obj) {
// return false;
// }
// return true;
// }
// Accepted solution for LeetCode #2727: Is Object Empty
function isEmpty(obj: Record<string, any> | any[]): boolean {
for (const x in obj) {
return false;
}
return true;
}
Use this to step through a reusable interview workflow for this problem.
Two nested loops check every pair or subarray. The outer loop fixes a starting point, the inner loop extends or searches. For n elements this gives up to n²/2 operations. No extra space, but the quadratic time is prohibitive for large inputs.
Most array problems have an O(n²) brute force (nested loops) and an O(n) optimal (single pass with clever state tracking). The key is identifying what information to maintain as you scan: a running max, a prefix sum, a hash map of seen values, or two pointers.
Review these before coding to avoid predictable interview regressions.
Wrong move: Loop endpoints miss first/last candidate.
Usually fails on: Fails on minimal arrays and exact-boundary answers.
Fix: Re-derive loops from inclusive/exclusive ranges before coding.