Concurrency · interview question
A teammate submits shaky cancellation code. Which review comment is the strongest?
Multiple choiceMediumchapter-15-curatedpremiumconcurrencycancellation
Answer and explanation
Correct answer
B. Make the rule clearer and easier to explain. Make cancellation behavior explicit so tasks stop cleanly and partial work is understood.
Why
The best review comment anchors the change to readability, correctness, and future maintenance. Ignoring cancellation leaves stray work running after the caller has already moved on.
Test yourself on Concurrency
A free test with instant, explained results. No account needed.
More Concurrency questions
- If you wrote a test around cancellation, what should the test prove first?
- What production risk should you worry about most if cancellation is handled lazily?
- Which option treats cancellation as an engineering policy decision instead of a syntax trick?
- Which option describes the most likely pitfall around cancellation?
- What does a strong engineer do when reasoning through cancellation code?
- You cannot rewrite everything today. What is the best incremental improvement around async def and await?