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.
You have n bags numbered from 0 to n - 1. You are given two 0-indexed integer arrays capacity and rocks. The ith bag can hold a maximum of capacity[i] rocks and currently contains rocks[i] rocks. You are also given an integer additionalRocks, the number of additional rocks you can place in any of the bags.
Return the maximum number of bags that could have full capacity after placing the additional rocks in some bags.
Example 1:
Input: capacity = [2,3,4,5], rocks = [1,2,4,4], additionalRocks = 2 Output: 3 Explanation: Place 1 rock in bag 0 and 1 rock in bag 1. The number of rocks in each bag are now [2,3,4,4]. Bags 0, 1, and 2 have full capacity. There are 3 bags at full capacity, so we return 3. It can be shown that it is not possible to have more than 3 bags at full capacity. Note that there may be other ways of placing the rocks that result in an answer of 3.
Example 2:
Input: capacity = [10,2,2], rocks = [2,2,0], additionalRocks = 100 Output: 3 Explanation: Place 8 rocks in bag 0 and 2 rocks in bag 2. The number of rocks in each bag are now [10,2,2]. Bags 0, 1, and 2 have full capacity. There are 3 bags at full capacity, so we return 3. It can be shown that it is not possible to have more than 3 bags at full capacity. Note that we did not use all of the additional rocks.
Constraints:
n == capacity.length == rocks.length1 <= n <= 5 * 1041 <= capacity[i] <= 1090 <= rocks[i] <= capacity[i]1 <= additionalRocks <= 109Problem summary: You have n bags numbered from 0 to n - 1. You are given two 0-indexed integer arrays capacity and rocks. The ith bag can hold a maximum of capacity[i] rocks and currently contains rocks[i] rocks. You are also given an integer additionalRocks, the number of additional rocks you can place in any of the bags. Return the maximum number of bags that could have full capacity after placing the additional rocks in some bags.
Start with the most direct exhaustive search. That gives a correctness anchor before optimizing.
Pattern signal: Array · Greedy
[2,3,4,5] [1,2,4,4] 2
[10,2,2] [2,2,0] 100
capacity-to-ship-packages-within-d-days)maximum-units-on-a-truck)Source-backed implementations are provided below for direct study and interview prep.
// Accepted solution for LeetCode #2279: Maximum Bags With Full Capacity of Rocks
class Solution {
public int maximumBags(int[] capacity, int[] rocks, int additionalRocks) {
int n = rocks.length;
for (int i = 0; i < n; ++i) {
capacity[i] -= rocks[i];
}
Arrays.sort(capacity);
for (int i = 0; i < n; ++i) {
additionalRocks -= capacity[i];
if (additionalRocks < 0) {
return i;
}
}
return n;
}
}
// Accepted solution for LeetCode #2279: Maximum Bags With Full Capacity of Rocks
func maximumBags(capacity []int, rocks []int, additionalRocks int) int {
for i, x := range rocks {
capacity[i] -= x
}
sort.Ints(capacity)
for i, x := range capacity {
additionalRocks -= x
if additionalRocks < 0 {
return i
}
}
return len(capacity)
}
# Accepted solution for LeetCode #2279: Maximum Bags With Full Capacity of Rocks
class Solution:
def maximumBags(
self, capacity: List[int], rocks: List[int], additionalRocks: int
) -> int:
for i, x in enumerate(rocks):
capacity[i] -= x
capacity.sort()
for i, x in enumerate(capacity):
additionalRocks -= x
if additionalRocks < 0:
return i
return len(capacity)
// Accepted solution for LeetCode #2279: Maximum Bags With Full Capacity of Rocks
impl Solution {
pub fn maximum_bags(mut capacity: Vec<i32>, rocks: Vec<i32>, mut additional_rocks: i32) -> i32 {
for i in 0..rocks.len() {
capacity[i] -= rocks[i];
}
capacity.sort();
for i in 0..capacity.len() {
additional_rocks -= capacity[i];
if additional_rocks < 0 {
return i as i32;
}
}
capacity.len() as i32
}
}
// Accepted solution for LeetCode #2279: Maximum Bags With Full Capacity of Rocks
function maximumBags(capacity: number[], rocks: number[], additionalRocks: number): number {
const n = rocks.length;
for (let i = 0; i < n; ++i) {
capacity[i] -= rocks[i];
}
capacity.sort((a, b) => a - b);
for (let i = 0; i < n; ++i) {
additionalRocks -= capacity[i];
if (additionalRocks < 0) {
return i;
}
}
return n;
}
Use this to step through a reusable interview workflow for this problem.
Try every possible combination of choices. With n items each having two states (include/exclude), the search space is 2ⁿ. Evaluating each combination takes O(n), giving O(n × 2ⁿ). The recursion stack or subset storage uses O(n) space.
Greedy algorithms typically sort the input (O(n log n)) then make a single pass (O(n)). The sort dominates. If the input is already sorted or the greedy choice can be computed without sorting, time drops to O(n). Proving greedy correctness (exchange argument) is harder than the implementation.
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: Locally optimal choices may fail globally.
Usually fails on: Counterexamples appear on crafted input orderings.
Fix: Verify with exchange argument or monotonic objective before committing.