Concurrency · interview question
What is the clearest sign that code around cancellation should be refactored?
Multiple choiceMediumchapter-15-curatedpremiumconcurrencycancellation
Answer and explanation
Correct answer
D. When the rule is no longer easy to trace, explain, or change without breaking nearby behavior.
Why
A refactor is justified when the code stops communicating its intent. Make cancellation behavior explicit so tasks stop cleanly and partial work is understood.
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?