Question
Which practice avoids a common mistake with Trees and Traversal Orders?
- Ignore the Trees and Traversal Orders issue and rely on team discipline instead of clearer APIs or invariants.
- Silence the Trees and Traversal Orders problem by using broad catches, hidden globals, or extra shared mutable state.
- Prefer the version of Trees and Traversal Orders that makes behavior less predictable as long as the code still runs.
- Do not memorize traversal names without connecting them to what state becomes available at each visit point.
Hint
Look for the option that protects correctness instead of hiding the problem.
Answer and rationale
Correct answer: D. Do not memorize traversal names without connecting them to what state becomes available at each visit point.
Do not memorize traversal names without connecting them to what state becomes available at each visit point. This is a common failure mode in real Python code and a frequent interview follow-up.
Track: Python