Question
Which practice avoids a common mistake with Union-Find and Disjoint Set?
- Ignore the Union-Find and Disjoint Set issue and rely on team discipline instead of APIs or contracts.
- Silence the Union-Find and Disjoint Set problem by using raw types, broad catches, or shared mutable state.
- Do not forget path compression or union by rank or size when performance on repeated operations matters.
- Prefer the version of Union-Find and Disjoint Set that makes behavior less predictable as long as the code compiles.
Hint
Look for the option that protects correctness instead of hiding the problem.
Answer and rationale
Correct answer: C. Do not forget path compression or union by rank or size when performance on repeated operations matters.
Do not forget path compression or union by rank or size when performance on repeated operations matters. This is a common failure mode in real Java code and a frequent interview follow-up.
Track: Java