Skip to main content

LeetCode 1760 Explained: Binary Search on Answer with Clear possible() Function Intuition

LeetCode 1760: Minimum Limit of Balls in a Bag (Binary Search on Answer)

LeetCode 1760 is a classic example of the Binary Search on Answer pattern. While many tutorials explain the binary search part, they often skip the most important piece — how the feasibility (possible) function actually works.

In this article, we will focus on building the intuition behind the solution, especially the logic used to count operations inside the possible() function.


🔹 Problem Overview

You are given an array nums where each element represents the number of balls in a bag. You are allowed to perform at most maxOperations operations.

In one operation, you can split a bag into two bags with any positive number of balls. Your goal is to minimize the maximum number of balls in any bag.


🔹 Why Binary Search Works Here

We are not searching inside the array. Instead, we are searching for the minimum possible maximum value after all allowed operations.

The answer range is clearly bounded:

  • Minimum possible value → 1
  • Maximum possible value → max(nums)

Since the feasibility of a value is monotonic (if a value works, all larger values work), binary search is the optimal approach.


🔹 What Does mid Represent?

During binary search, mid represents a candidate answer:

Can we make every bag have at most mid balls using at most maxOperations splits?

This turns the problem into a simple YES / NO decision — perfect for binary search.


🔹 Understanding the possible() Function

This is the most important part of the solution. For each bag with i balls, we calculate how many operations are required to ensure that no resulting bag exceeds mid.

The formula used is:

operations += ceil(i / mid) - 1
  

Why This Works

If a bag has i balls and we want each part to be at most mid, we need:

  • ceil(i / mid) total pieces
  • Number of operations = pieces − 1

The subtraction of 1 is crucial. Even when a value is perfectly divisible, counting pieces directly would overestimate the number of operations.


🔹 Early Stopping Optimization

If at any point the required operations exceed maxOperations, we immediately return false.

This keeps the algorithm efficient and avoids unnecessary computation.


🔹 Complete Python Solution

from math import ceil

class Solution:
    def possible(self, nums, maxOperations, mid):
        opr = 0
        for i in nums:
            opr += ceil(i / mid) - 1
            if opr > maxOperations:
                return False
        return True

    def minimumSize(self, nums, maxOperations):
        s = 1
        l = max(nums)

        while s < l:
            mid = (s + l) // 2
            if self.possible(nums, maxOperations, mid):
                l = mid
            else:
                s = mid + 1

        return s
  

🔹 Time and Space Complexity

  • Time Complexity: O(n log max(nums))
  • Space Complexity: O(1)

🔹 Final Takeaway

This problem is not just about binary search — it is about correctly modeling the number of operations required to enforce a constraint.

Once you understand how ceil(i / mid) - 1 works, this entire class of problems becomes much easier to solve.

This same pattern appears in many interview problems where the goal is to minimize a maximum value under limited operations.

🔗 Full source code available here: GitHub – LeetCode 1760 Solution

Comments

Popular posts from this blog

LeetCode 88 Explained: Four Approaches, Mistakes, Fixes & the Final Optimal Python Solution

Evolving My Solution to “Merge Sorted Array” A practical, beginner-friendly walkthrough showing four versions of my code (from a naive approach to the optimal in-place two-pointer solution). Includes explanations, complexity and ready-to-paste code. Problem Summary You are given two sorted arrays: nums1 with size m + n (first m are valid) nums2 with size n Goal: Merge nums2 into nums1 in sorted order in-place . Version 1 — Beginner Approach (Extra List) I merged into a new list then copied back. Works, but not in-place and uses extra memory. class Solution: def merge(self, nums1, m, nums2, n): result = [] p1 = 0 p2 = 0 for _ in range(m+n): if p1 >= m: result.extend(nums2[p2:n]) break elif p2 >= n: result.extend(nums1[p1:m]) break elif nu...

Introducing CodeMad: Your Ultimate Universal IDE with Custom Shortcuts

Introducing CodeMad: Your Ultimate Multi-Language IDE with Custom Shortcuts Welcome to the world of CodeMad, your all-in-one Integrated Development Environment (IDE) that simplifies coding and boosts productivity. Developed in Python, CodeMad is designed to make your coding experience smoother and more efficient across a variety of programming languages, including C, C++, Java, Python, and HTML. Whether you're a beginner or an experienced programmer, CodeMad is your go-to tool. In this blog, we'll dive deep into the workings of CodeMad, highlighting its unique features and easy installation process. The Power of Shortcuts CodeMad's intuitive interface is built around a set of powerful keyboard shortcuts that make coding a breeze. Here are some of the key shortcuts you'll find in CodeMad: Copy (Ctrl+C) : Duplicate text with ease. Paste (Ctrl+V) : Quickly insert copied content into your code. Undo (Ctrl+Z) and Redo (Ctrl+Y) : Correct mistakes and s...

Product of Array Except Self in Python | Prefix & Suffix Explained (LeetCode 238)

Problem Overview The Product of Array Except Self is a classic problem that tests your understanding of array traversal and optimization. The task is simple to state but tricky to implement efficiently. Given an integer array nums , you need to return an array such that each element at index i is equal to the product of all the elements in nums except nums[i] . The challenge is that: Division is not allowed The solution must run in O(n) time Initial Thoughts At first glance, it feels natural to compute the total product of the array and divide it by the current element. However, this approach fails because division is forbidden and handling zeroes becomes messy. This pushed me to think differently — instead of excluding the current element, why not multiply everything around it? That’s where the prefix and suffix product pattern comes in. Key Insight: Prefix & Suffix Products For every index i : Prefix product → product of all elements to t...