Comments on: Immutable objects in C# http://www.stevecooper.org/2009/07/14/immutable-objects-in-c/ Programming, writing, programming about writing. Wed, 10 Mar 2010 22:25:23 +0000 http://wordpress.org/?v=2.7.1 hourly 1 By: Deployment Zone » Side Effect Free Retrieval Pattern http://www.stevecooper.org/2009/07/14/immutable-objects-in-c/comment-page-1/#comment-9185 Deployment Zone » Side Effect Free Retrieval Pattern Thu, 16 Jul 2009 16:55:32 +0000 http://www.stevecooper.org/?p=75#comment-9185 <p>[...] ICloneable reference type is pretty much required, though any immutable reference type could get by without cloning because any changes gives you a new copy of that [...]</p> [...] ICloneable reference type is pretty much required, though any immutable reference type could get by without cloning because any changes gives you a new copy of that [...]

]]> By: Charles Feduke http://www.stevecooper.org/2009/07/14/immutable-objects-in-c/comment-page-1/#comment-9180 Charles Feduke Tue, 14 Jul 2009 18:05:25 +0000 http://www.stevecooper.org/?p=75#comment-9180 <p>Great. I have been bitten by non-immutable types in a couple different ways - once where I inadvertently changed the contents of a cached object (dumb on me, but immutables would have prevents such brash actions) and every time I expose "default" instances (primarily for lookup table entries associated with a property from one of my model classes).</p> <p>Of course migrating the necessary code to immutable structs is a huge task in of itself... and the places where I'd find the most benefits for immutable types already contain rich class hierarchies that are difficult to clone without a DeepCopy implementation.</p> Great. I have been bitten by non-immutable types in a couple different ways - once where I inadvertently changed the contents of a cached object (dumb on me, but immutables would have prevents such brash actions) and every time I expose “default” instances (primarily for lookup table entries associated with a property from one of my model classes).

Of course migrating the necessary code to immutable structs is a huge task in of itself… and the places where I’d find the most benefits for immutable types already contain rich class hierarchies that are difficult to clone without a DeepCopy implementation.

]]>