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.
Move from brute-force thinking to an efficient approach using array strategy.
Given an integer array arr and an integer difference, return the length of the longest subsequence in arr which is an arithmetic sequence such that the difference between adjacent elements in the subsequence equals difference.
A subsequence is a sequence that can be derived from arr by deleting some or no elements without changing the order of the remaining elements.
Example 1:
Input: arr = [1,2,3,4], difference = 1 Output: 4 Explanation: The longest arithmetic subsequence is [1,2,3,4].
Example 2:
Input: arr = [1,3,5,7], difference = 1 Output: 1 Explanation: The longest arithmetic subsequence is any single element.
Example 3:
Input: arr = [1,5,7,8,5,3,4,2,1], difference = -2 Output: 4 Explanation: The longest arithmetic subsequence is [7,5,3,1].
Constraints:
1 <= arr.length <= 105-104 <= arr[i], difference <= 104Problem summary: Given an integer array arr and an integer difference, return the length of the longest subsequence in arr which is an arithmetic sequence such that the difference between adjacent elements in the subsequence equals difference. A subsequence is a sequence that can be derived from arr by deleting some or no elements without changing the order of the remaining elements.
Start with the most direct exhaustive search. That gives a correctness anchor before optimizing.
Pattern signal: Array · Hash Map · Dynamic Programming
[1,2,3,4] 1
[1,3,5,7] 1
[1,5,7,8,5,3,4,2,1] -2
destroy-sequential-targets)Source-backed implementations are provided below for direct study and interview prep.
// Accepted solution for LeetCode #1218: Longest Arithmetic Subsequence of Given Difference
class Solution {
public int longestSubsequence(int[] arr, int difference) {
Map<Integer, Integer> f = new HashMap<>();
int ans = 0;
for (int x : arr) {
f.put(x, f.getOrDefault(x - difference, 0) + 1);
ans = Math.max(ans, f.get(x));
}
return ans;
}
}
// Accepted solution for LeetCode #1218: Longest Arithmetic Subsequence of Given Difference
func longestSubsequence(arr []int, difference int) (ans int) {
f := map[int]int{}
for _, x := range arr {
f[x] = f[x-difference] + 1
ans = max(ans, f[x])
}
return
}
# Accepted solution for LeetCode #1218: Longest Arithmetic Subsequence of Given Difference
class Solution:
def longestSubsequence(self, arr: List[int], difference: int) -> int:
f = defaultdict(int)
for x in arr:
f[x] = f[x - difference] + 1
return max(f.values())
// Accepted solution for LeetCode #1218: Longest Arithmetic Subsequence of Given Difference
use std::collections::HashMap;
impl Solution {
pub fn longest_subsequence(arr: Vec<i32>, difference: i32) -> i32 {
let mut f = HashMap::new();
let mut ans = 0;
for &x in &arr {
let count = f.get(&(x - difference)).unwrap_or(&0) + 1;
f.insert(x, count);
ans = ans.max(count);
}
ans
}
}
// Accepted solution for LeetCode #1218: Longest Arithmetic Subsequence of Given Difference
function longestSubsequence(arr: number[], difference: number): number {
const f: Map<number, number> = new Map();
for (const x of arr) {
f.set(x, (f.get(x - difference) ?? 0) + 1);
}
return Math.max(...f.values());
}
Use this to step through a reusable interview workflow for this problem.
Pure recursion explores every possible choice at each step. With two choices per state (take or skip), the decision tree has 2ⁿ leaves. The recursion stack uses O(n) space. Many subproblems are recomputed exponentially many times.
Each cell in the DP table is computed exactly once from previously solved subproblems. The table dimensions determine both time and space. Look for the state variables — each unique combination of state values is one cell. Often a rolling array can reduce space by one dimension.
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.
Wrong move: Zero-count keys stay in map and break distinct/count constraints.
Usually fails on: Window/map size checks are consistently off by one.
Fix: Delete keys when count reaches zero.
Wrong move: An incomplete state merges distinct subproblems and caches incorrect answers.
Usually fails on: Correctness breaks on cases that differ only in hidden state.
Fix: Define state so each unique subproblem maps to one DP cell.