We're sorry but this page doesn't work properly without JavaScript enabled. Please enable it to continue.
Feedback

The changing state of immutability C#

Formal Metadata

Title
The changing state of immutability C#
Title of Series
Number of Parts
133
Author
License
CC Attribution - NonCommercial - ShareAlike 3.0 Unported:
You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal and non-commercial purpose as long as the work is attributed to the author in the manner specified by the author or licensor and the work or content is shared also in adapted form only under the conditions of this
Identifiers
Publisher
Release Date
Language

Content Metadata

Subject Area
Genre
Abstract
Immutability rocks, right? When a type is immutable, it's usually easier to reason about your code, easier to share data safely, and easier to make money ooze from every USB port. That's the promise, at least. I heard an F# developer say it, so it must be true. Unfortunately, when a language or platform isn't designed to encourage immutability, immutability can introduce its own pain points - and sometimes they can be subtle. Come with me on a journey of exploring different options forimplementing immutability in C#, see how it's become somewhat simpler over the various versions, and consider what the future *might* have in store.