Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
It is obvious that immutability increases the re-usability since it creates new object in each state change.Can somebody tells me a practical scenario where we need a immutable class ?
Consider
java.lang.String. If it weren’t immutable, every time you ever have a string you want to be confident wouldn’t change underneath you, you’d have to create a copy.Another example is collections: it’s nice to be able to accept or return a genuinely immutable collection (e.g. from Guava – not just an immutable view on a mutable collection) and have confidence that it won’t be changed.
Whether those count as “needs” or not, I don’t know – but I wouldn’t want to develop without them.