Question
Which practice avoids a common mistake with Polymorphism, Overloading, and Overriding?
- Ignore the Polymorphism, Overloading, and Overriding issue and rely on team discipline instead of APIs or contracts.
- Do not expect overload resolution to depend on the runtime type of the argument or reference.
- Silence the Polymorphism, Overloading, and Overriding problem by using raw types, broad catches, or shared mutable state.
- Prefer the version of Polymorphism, Overloading, and Overriding 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: B. Do not expect overload resolution to depend on the runtime type of the argument or reference.
Do not expect overload resolution to depend on the runtime type of the argument or reference. This is a common failure mode in real Java code and a frequent interview follow-up.
Track: Java