问题
We know the concept of immutability but need to know few immutable types other than
- String
- DateTime
Are there more?
回答1:
A list of immutable types in the framework class library follows below. (Feel free to expand it!)
System.…
- All primitive value types: (Note: not all value types are immutable!)
ByteandSByteInt16andUInt16Int32andUInt32Int64andUInt64IntPtrSingleDouble
DecimalAll anonymous types created by the compiler ((Wrong for two reasons: These types are not in the FCL, and apparently VB.NET types are mutable.)new { ... }in C#,New With { ... }in VB.NET)- All enumeration types (
enum,Enum) - All delegate types. (see this answer. While it might seem that delegates are mutable (since you can do things like
obj.PropertyChanged += callback, it's actually theobj.PropertyChangedreference that is mutated to point to a newly constructed delegate instance; the original delegate instance stays unchanged.) DateTime,TimeSpan(mentioned in this answer) andDateTimeOffsetDBNullGuidNullable<T>String- The
Tuple<…>types introduced with .NET 4 (mentioned in this answer) UriVersionVoid
System.Linq.…
Lookup<TKey, TElement>
回答2:
TimeSpan, or modern type family Tuple. Tuple is immutable cause it implemented to support functional languages (F# f.e.) in .NET.
Of course you can make your own classes and structures mutable or immutable, as you wish. Immutable types (aka value objects) are useful in multithreading programming, functional programming, to clear a code.
To make a class or struct immutable just remove all public/protected/internal setters; and better declare all fields with readonly keyword.
回答3:
I am not sure if you're looking for publicly immutable types in .NET or types totally immutable at all. Furthermore you want to take care of only the public types in .NET? The deeper problem is defining what forms immutability. Does a class that only has
public readonly int[] Numbers;
makes it immutable? The Numbers itself can't be changed but its contents can be. You get the idea.
Anyway you could inspect yourself programmatically. For deeper nested checks you will need recursion (which I wont do here)
Load all assemblies you wanna check, and do something like (not tested)
var immutables = AppDomain.CurrentDomain
.GetAssemblies()
.SelectMany(t => t.GetTypes())
.Where(t => t
.GetProperties(your binding flags depending on your definition)
.All(p => !p.CanWrite)
&& t
.GetFields(your binding flags depending on your definition)
.All(f => f.IsInitOnly)
.ToList();
Even this wont be enough for finding immutability of collection types. Some of the immutable collection types (though not a part of default .NET core) can be found here: Immutable Collections
Some notable immutables:
- some class types like
String,Tuple, anonymous types - most structs (notable exceptions include most enumerators)
- enums
- delegates
immutable collection types like
ImmutableArray (prerelease version)
ImmutableDictionary
ImmutableSortedDictionary
ImmutableHashSet
ImmutableList
ImmutableQueue
ImmutableSortedSet
ImmutableStack
回答4:
Some examples from mscorlib:
- All of the primitive types
- enums
decimal(U)IntPtrDateTime,DateTimeOffset,TimeSpanKeyValuePair<,>- as an opposite,DictionaryEntryis not immutableTuple<...>(Multicast)Delegate- similarly to strings, always a new instance is returned when it is changed.GuidVersion
Interestingly, string is actually not really immutable; however, we can treat it as a "practically immutable" type, meaning, that the content of a string instance cannot be changed by the public ways (at least, in a safe context). But it has for example a wstrcpy internal method, which is used by the StringBuilder class to manipulate a string instance.
来源:https://stackoverflow.com/questions/31721466/examples-of-immutable-types-in-net