Enumerates the elements of a SortedSet<T> object.
Assembly: System (in System.dll)
Thegeneric type exposes the following members.
|Dispose||Releases all resources used by the .|
|Equals||Indicates whether this instance and a specified object are equal. (Inherited from ValueType.)|
|GetHashCode||Returns the hash code for this instance. (Inherited from ValueType.)|
|GetType||Gets the Type of the current instance. (Inherited from Object.)|
|MoveNext||Advances the enumerator to the next element of the SortedSet<T> collection.|
|ToString||Returns the fully qualified type name of this instance. (Inherited from ValueType.)|
|IDeserializationCallback.OnDeserialization||Implements the System.Runtime.Serialization.ISerializable interface and raises the deserialization event when the deserialization is complete.|
|IEnumerator.Current||Gets the element at the current position of the enumerator.|
|IEnumerator.Reset||Sets the enumerator to its initial position, which is before the first element in the collection.|
|ISerializable.GetObjectData||Implements the System.Runtime.Serialization.ISerializable interface and returns the data needed to serialize the SortedSet<T> instance.|
The foreach statement of the C# language (for each in C++, For Each in Visual Basic) hides the complexity of enumerators. Therefore, using foreach is recommended, instead of directly manipulating the enumerator.
IDisposable interface. When you have finished using the type, you should dispose of it either directly or indirectly. To dispose of the type directly, call its Dispose method in atry/catch block. To dispose of it indirectly, use a language construct such as using (in C#) or Using (in Visual Basic). For more information, see the “Using an Object that Implements IDisposable” section in the IDisposable interface topic.
Enumerators can be used to read the data in the collection, but they cannot be used to modify the underlying collection.
Initially, the enumerator is positioned before the first element in the collection. At this position, the Current property is undefined. Therefore, you must call the MoveNext method to advance the enumerator to the first element of the collection before reading the value of Current.
If MoveNext passes the end of the collection, the enumerator is positioned after the last element in the collection and MoveNext returns false. When the enumerator is at this position, subsequent calls to MoveNext also return false. If the last call to MoveNext returned false, Current is undefined. You cannot set Current to the first element of the collection again; you must create a new enumerator object instead.
An enumerator remains valid as long as the collection remains unchanged. If changes are made to the collection, such as adding, modifying, or deleting elements, the enumerator is irrecoverably invalidated and its behavior is undefined.
The enumerator does not have exclusive access to the collection; therefore, enumerating through a collection is intrinsically not a thread-safe procedure. To guarantee thread safety during enumeration, you can lock the collection during the entire enumeration. To allow the collection to be accessed by multiple threads for reading and writing, you must implement your own synchronization.
Default implementations of collections in the System.Collections.Generic namespace are not synchronized.