Question
Which practice avoids a common mistake with java.time API?
- Ignore the java.time API issue and rely on team discipline instead of APIs or contracts.
- Silence the java.time API problem by using raw types, broad catches, or shared mutable state.
- Do not mix human calendar concepts with machine instants without explicit timezone conversion rules.
- Prefer the version of java.time API 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 mix human calendar concepts with machine instants without explicit timezone conversion rules.
Do not mix human calendar concepts with machine instants without explicit timezone conversion rules. This is a common failure mode in real Java code and a frequent interview follow-up.
Track: Java