Time: 0:00
Test a custom input to verify an edge case (e.g. empty lists, negative numbers, duplicates).
This bug belongs to the off-by-one errors pattern
The loop that runs one time too many, the slice that drops the last item, the index that starts in the wrong place.
What went wrong: low < n does not count n when it equals low, but n <= high does count high. The two ends are treated differently.
The fix: low <= n <= high
Remember: "including both ends" means <= on both sides. Test the exact end values.
The pattern behind it: off-by-one errors.
Paste this into any web page or blog post. Visitors fix the bug right there, in their browser.
<iframe src="https://trybughunt.com/embed/b4d8b9bf-5f2d-4a99-93a3-5ecee1384c5b" title="Debugging challenge: Range count skips the lowest value" width="100%" height="580" loading="lazy" style="border:1px solid #d4d4d8;border-radius:12px;max-width:760px"></iframe>
<p style="font-size:14px">Debugging challenge from <a href="https://trybughunt.com/challenges/b4d8b9bf-5f2d-4a99-93a3-5ecee1384c5b">TryBugHunt</a></p>