Question
Which practice avoids a common mistake with ArrayList vs LinkedList?
- Do not assume LinkedList is faster just because inserts conceptually avoid shifting elements.
- Ignore the ArrayList vs LinkedList issue and rely on team discipline instead of APIs or contracts.
- Silence the ArrayList vs LinkedList problem by using raw types, broad catches, or shared mutable state.
- Prefer the version of ArrayList vs LinkedList 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 assume LinkedList is faster just because inserts conceptually avoid shifting elements.
Do not assume LinkedList is faster just because inserts conceptually avoid shifting elements. This is a common failure mode in real Java code and a frequent interview follow-up.
Track: Java