Question
Which practice avoids a common mistake with Counter and Frequency Maps?
- Ignore the Counter and Frequency Maps issue and rely on team discipline instead of clearer APIs or invariants.
- Silence the Counter and Frequency Maps problem by using broad catches, hidden globals, or extra shared mutable state.
- Do not forget that zero and missing counts have slightly different semantics in certain Counter operations.
- Prefer the version of Counter and Frequency Maps that makes behavior less predictable as long as the code still runs.
Hint
Look for the option that protects correctness instead of hiding the problem.
Answer and rationale
Correct answer: C. Do not forget that zero and missing counts have slightly different semantics in certain Counter operations.
Do not forget that zero and missing counts have slightly different semantics in certain Counter operations. This is a common failure mode in real Python code and a frequent interview follow-up.
Track: Python