Additional Notes
How would you explain a design consequence of exposing mutable objects in an interview?
Track: Java
Topic: OOP
Focus: Access Modifiers and Visibility
Java: Access Modifiers and Visibility
Answer
It leads to unintended modifications. Frame the concept in practical terms so you can explain it during interview discussion.
Exposing mutable objects, like a list of items, allows external code to change the object state, possibly causing errors. For example, a 'Cart' class returning its items list directly can let other classes modify the cart's contents without control, leading to order processing issues.
Exposing mutable objects, like a list of items, allows external code to change the object state, possibly causing errors. For example, a 'Cart' class returning its items list directly can let other classes modify the cart's contents without control, leading to order processing issues.
Topics: Access Modifiers and Visibility Java OOP