Time: 0:00
Test a custom input to verify an edge case (e.g. empty lists, negative numbers, duplicates).
This bug belongs to the async and race conditions pattern
A missing await, unbuffered channel deadlocks, ConcurrentModificationException, and data races under load.
What went wrong: The goroutine captures the loop variable item by reference, leading to a race condition where the final value of item is used for all goroutines.
The fix: Pass the loop index and value as parameters to the goroutine to ensure each goroutine operates on its own copy.
Remember: In Go, variables in a loop are shared across iterations unless explicitly captured.
The pattern behind it: async and race conditions.
Paste this into any web page or blog post. Visitors fix the bug right there, in their browser.
<iframe src="https://trybughunt.com/embed/926c819b-8fbe-4bdc-8d60-a3b530650ada" title="Debugging challenge: Unexpected output in concurrent range loop processing" 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/926c819b-8fbe-4bdc-8d60-a3b530650ada">TryBugHunt</a></p>