Question
Which practice avoids a common mistake with Union-Find / Disjoint Set?
- Ignore the Union-Find / Disjoint Set issue and rely on team discipline instead of clearer APIs or invariants.
- Silence the Union-Find / Disjoint Set problem by using broad catches, hidden globals, or extra shared mutable state.
- Prefer the version of Union-Find / Disjoint Set that makes behavior less predictable as long as the code still runs.
- Do not skip path compression or union-by-rank-style heuristics when the problem depends on near-constant practical performance.
Hint
Look for the option that protects correctness instead of hiding the problem.
Answer and rationale
Correct answer: D. Do not skip path compression or union-by-rank-style heuristics when the problem depends on near-constant practical performance.
Do not skip path compression or union-by-rank-style heuristics when the problem depends on near-constant practical performance. This is a common failure mode in real Python code and a frequent interview follow-up.
Track: Python