Lock-free concurrent queue
You need to write a lock-free concurrent queue in Rust using atomics for a high-throughput message broker. A teammate says modern AI agents are great at Rust and suggests generating the whole structure, memory ordering and all. Make the judgment call: is this a good delegation? What failure modes specifically attach to AI-generated concurrent/unsafe code, and how does that change how you'd use the tool?
audit_atomic_trace(trace_rows: list[str]) → list[str][["t1|publish|head|release","t2|consume|head|acquire"]]out[][["t1|publish|head|relaxed","t2|consume|head|relaxed"]]out["0:publish_not_release","1:consume_not_acquire"][["t1|publish|head|relaxed","t2|consume|head|acquire"]]out["0:publish_not_release","1:unsynchronized_read"]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.
Vibe & agentic: describe the solution in plain language (or narrate it) and the coach grades your approach.