Talk:Immutable object

Java Stub‑class Low‑importance

	This article is within the scope of WikiProject Java, a collaborative effort to improve the coverage of Java on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.JavaWikipedia:WikiProject JavaTemplate:WikiProject JavaJava
Stub	This article has been rated as Stub-class on Wikipedia's content assessment scale.
Low	This article has been rated as Low-importance on the project's importance scale.

Untitled

there is an error: ImmutableCart is immutable only if elements of the list are themselves immutable. Otheriwse, you copy the list allright, but you share the elements with the caller, so he can mutate them as he pleases. —Preceding unsigned comment added by 128.30.84.40 (talk • contribs) 18:40, 19 November 2005

I disagree. It depends on what you consider part of the "ImmutableCart" object. I consider an "ImmutableCart" object to contain only its fields, i.e. the reference "items". Under this definition, "ImmutableCart" is indeed immutable. --Spoon! 09:03, 18 March 2007 (UTC)[reply]

Wouldn't this imply that the Cart class is immutable too? I.e. the 'items' reference never changes (although its contents may change). Zedoo (talk) 18:28, 16 August 2008 (UTC)[reply]

I changed all references to vector in the C++ example to std::vector, as the C++ example would presumably be in a header file and it is generally considered bad style to include a global using namespace directive in a header file. I think it's very important for code examples to exhibit good style even if that makes them a little more verbose. - Zixyer 02:24, 19 December 2005 (UTC)[reply]

why does defensive copying link to object (computer science) which has no information as to what "defensive copying" means probably a mistake, can somebody correct? --Alex 11:10, 30 December 2005 (UTC)[reply]

I changed the defensive copy redirect to go to Object copy instead, which talks about defensive copying.Tim Dean 22:07, 31 December 2005 (UTC)[reply]

List to Array to List?

I'm not a C# guy so I was afraid to make the change myself, but does anyone else see anything wacky about ImmutableCart's constructor? I checked the docs and it looks like List has a constructor that takes a collection as an argument, presumably creating a new list containing the same objects as the old one.

Is there a good reason why the example takes the input List, turns it into an array, then turns it into a new List? Guess I'll just make the change... tfrey 21:31, 14 April 2008 (UTC)

Because it's not C# but Java, and List is (last time I checked) not a class and cannot be instantiated. I'm reverting the change. -- Taku (talk) 11:53, 4 May 2008 (UTC)[reply]

But wouldn't Collections.unmodifiableList(items) be better in both cases? --131.159.0.7 (talk) 14:57, 14 June 2008 (UTC)[reply]

No, because Collections.unmodifiableList(items) doesn't create a copy of a list. items.toArray(), on the other hand, gives a copy of an array (not the underlying array.) -- Taku (talk) 20:55, 14 June 2008 (UTC)[reply]

Merge

I didn't propose the merge, but I agree it sounds like a good idea. Regards, Ben Aveling 09:00, 7 September 2008 (UTC)[reply]

Need for disambiguation

"Mutability" is also used in the biological sciences. E.g. In Voet&Voet, 2011, p3, "Life possesses the properties of replication, catalysis, and mutability." 86.184.76.240 (talk) 16:02, 20 January 2011 (UTC)[reply]