Additional Notes
Why avoid exposing mutable static fields?
Track: Java
Topic: Core Java
Focus: Code Reading and State Safety
Java: Code Reading and State Safety
Answer
They can be changed from anywhere, leading to inconsistent states.
Mutable static fields are shared across all instances of a class, meaning any change affects all instances. This can lead to unpredictable behavior. In an e-commerce system, a static `discountRate` in a `Product` class should be final to avoid inconsistent pricing across products.
Mutable static fields are shared across all instances of a class, meaning any change affects all instances. This can lead to unpredictable behavior. In an e-commerce system, a static `discountRate` in a `Product` class should be final to avoid inconsistent pricing across products.
Topics: Code Reading and State Safety Core Java Java