Question
Which practice avoids a common mistake with HashSet Membership and Deduplication?
- Do not forget that HashSet correctness depends on consistent equals and hashCode behavior for custom element types.
- Ignore the HashSet Membership and Deduplication issue and rely on team discipline instead of APIs or contracts.
- Silence the HashSet Membership and Deduplication problem by using raw types, broad catches, or shared mutable state.
- Prefer the version of HashSet Membership and Deduplication 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: A. Do not forget that HashSet correctness depends on consistent equals and hashCode behavior for custom element types.
Do not forget that HashSet correctness depends on consistent equals and hashCode behavior for custom element types. This is a common failure mode in real Java code and a frequent interview follow-up.
Track: Java