Goroutine closure variable capture
You ask an AI to explain this Go worker-fan-out so you can extend it. The agent says: "It launches one goroutine per job and each goroutine processes its own job concurrently — clean and correct." The codebase is on Go 1.20. Is the explanation correct, and how do you verify the per-goroutine claim before you build on it?
Implement
resolve_captured_jobs(job_ids: list[str], run_after_index: list[int], go_minor: int) → list[str]Examples
in
[["j1","j2","j3"],[2,2,2],20]out["j3","j3","j3"]in
[["j1","j2","j3"],[2,2,2],22]out["j1","j2","j3"]What a strong answer looks like
Treat the AI’s output as a draft to verify, not an answer to trust. Name the specific flaw and the input that triggers it, say how you’d catch it (tests, edge cases, reading critically), and how you’d re-prompt or decompose to get it right.
0:00 of about 18 min
Vibe & agentic: describe the solution in plain language (or narrate it) and the coach grades your approach.
Which questions mattered is sealed until you submit. Telling you now would just be handing over the edge cases.
Run or narrate your approach, then ask the coach.