Question
Which practice avoids a common mistake with Singly Linked Lists?
- Do not describe linked lists as automatically fast overall when traversal still costs time and object overhead is high.
- Ignore the Singly Linked Lists issue and rely on team discipline instead of APIs or contracts.
- Silence the Singly Linked Lists problem by using raw types, broad catches, or shared mutable state.
- Prefer the version of Singly Linked Lists 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 describe linked lists as automatically fast overall when traversal still costs time and object overhead is high.
Do not describe linked lists as automatically fast overall when traversal still costs time and object overhead is high. This is a common failure mode in real Java code and a frequent interview follow-up.
Track: Java