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: In Rust, the syntax 0..=len creates an inclusive range that includes the end bound len. Slicing with [0..=len] tries to access the element at index len, which is past the end of the slice and causes a panic.
The fix: Use half-open range 0..len instead of inclusive range 0..=len.
Remember: Slice indices are 0-based; valid upper bounds for half-open ranges are 0..len.
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/cdbdd642-dfb7-40e3-adfa-05408cc10f97" title="Debugging challenge: Off-by-one inclusive range panic in slice window" 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/cdbdd642-dfb7-40e3-adfa-05408cc10f97">TryBugHunt</a></p>