Question
Which practice avoids a common mistake with Sets and Membership Testing?
- Ignore the Sets and Membership Testing issue and rely on team discipline instead of clearer APIs or invariants.
- Silence the Sets and Membership Testing problem by using broad catches, hidden globals, or extra shared mutable state.
- Prefer the version of Sets and Membership Testing that makes behavior less predictable as long as the code still runs.
- Do not choose a set when stable order or duplicate counts are required by the problem.
Hint
Look for the option that protects correctness instead of hiding the problem.
Answer and rationale
Correct answer: D. Do not choose a set when stable order or duplicate counts are required by the problem.
Do not choose a set when stable order or duplicate counts are required by the problem. This is a common failure mode in real Python code and a frequent interview follow-up.
Track: Python