Question
What deeper point about TreeSet and NavigableSet should a senior Java developer mention?
- At senior level, the right answer is that TreeSet and NavigableSet exists mostly for historical syntax reasons.
- A senior answer highlights that navigable sets are often chosen for boundary queries, not merely for sorted printing.
- At senior level, the JVM removes the tradeoffs around TreeSet and NavigableSet, so design choices barely matter.
- At senior level, any approach to TreeSet and NavigableSet is equally correct if it compiles and passes a small test.
Hint
Look beyond syntax and explain the runtime, API, or design consequence.
Answer and rationale
Correct answer: B. A senior answer highlights that navigable sets are often chosen for boundary queries, not merely for sorted printing.
A senior answer highlights that navigable sets are often chosen for boundary queries, not merely for sorted printing. This is the kind of tradeoff-aware answer senior interviews usually expect.
Track: Java