Question
Which practice avoids a common mistake with Dynamic Arrays and Resizing?
- Ignore the Dynamic Arrays and Resizing issue and rely on team discipline instead of APIs or contracts.
- Do not optimize only for the rare resize event and ignore that repeated front insertions still cause costly element shifts.
- Silence the Dynamic Arrays and Resizing problem by using raw types, broad catches, or shared mutable state.
- Prefer the version of Dynamic Arrays and Resizing 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 optimize only for the rare resize event and ignore that repeated front insertions still cause costly element shifts.
Do not optimize only for the rare resize event and ignore that repeated front insertions still cause costly element shifts. This is a common failure mode in real Java code and a frequent interview follow-up.
Track: Java