Question
Which practice avoids a common mistake with Hash Tables and Hashing?
- Ignore the Hash Tables and Hashing issue and rely on team discipline instead of APIs or contracts.
- Silence the Hash Tables and Hashing problem by using raw types, broad catches, or shared mutable state.
- Do not talk about hashing as magic constant time without mentioning collisions and key-equality rules.
- Prefer the version of Hash Tables and Hashing 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 talk about hashing as magic constant time without mentioning collisions and key-equality rules.
Do not talk about hashing as magic constant time without mentioning collisions and key-equality rules. This is a common failure mode in real Java code and a frequent interview follow-up.
Track: Java