Time: 0:00
Test a custom input to verify an edge case (e.g. empty lists, negative numbers, duplicates).
This bug belongs to the scope and closure bugs pattern
Every callback reports the last value, a counter never increments, UnboundLocalError on a variable you can see.
What went wrong: The closure captures `data` by value (move semantics), making it unavailable for further use in the function.
The fix: Ensure `data` is not needed after the closure or clone it before passing to `process_data`.
Remember: In Rust, closures capture variables by value by default, which can lead to moved values becoming inaccessible.
The pattern behind it: scope and closure bugs.
Paste this into any web page or blog post. Visitors fix the bug right there, in their browser.
<iframe src="https://trybughunt.com/embed/6786311b-7756-40b1-ba33-7af77cf7fc85" title="Debugging challenge: Variable inaccessible after closure use in Rust" 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/6786311b-7756-40b1-ba33-7af77cf7fc85">TryBugHunt</a></p>