Explain closure capture.
Skip to solutionKEEP THE
hardDSA
What is the late-binding closure pitfall in loops?
351 views
01
Understand the problem
closureslate-binding
02
Attempt it yourself
Sketch your approach before reading the solution — that's what interviews test.
Nudge consolestandby
Stuck? Beam a request up — the console returns a conceptual nudge that guides your logic without spoiling the implementation.
03
Study the solution
Closures capture variables by reference, not value, so functions created in a loop all see the final loop value ([lambda: i for i in range(3)] all return 2). Fix it by binding per-iteration with a default arg: lambda i=i: i.
Solution ready — 2 min read
Classified // press E to declassify
04
Run the code
PYAll closures see the final i — and three fixes
05
Join the discussion
Discussion (0)
Sign in to join the discussion.
No responses yet. Be the first to share what you think.
Transmission complete // awaiting log
KEEP THE
STREAK ALIVE.
Dossier 112 of 120 decoded in the Python track. One more won't hurt.