Spliterators.AbstractSpliterator.InterfaceConsts.Concurrent Field
Definition
Important
Some information relates to prerelease product that may be substantially modified before it’s released. Microsoft makes no warranties, express or implied, with respect to the information provided here.
Caution
This constant will be removed in the future version. Use Java.Util.SpliteratorCharacteristics enum directly instead of this field.
Characteristic value signifying that the element source may be safely concurrently modified (allowing additions, replacements, and/or removals) by multiple threads without external synchronization.
[Android.Runtime.Register("CONCURRENT", ApiSince=24)]
[System.Obsolete("This constant will be removed in the future version. Use Java.Util.SpliteratorCharacteristics enum directly instead of this field.", true)]
public const Java.Util.SpliteratorCharacteristics Concurrent = 4096;[<Android.Runtime.Register("CONCURRENT", ApiSince=24)>]
[<System.Obsolete("This constant will be removed in the future version. Use Java.Util.SpliteratorCharacteristics enum directly instead of this field.", true)>]
val mutable Concurrent : Java.Util.SpliteratorCharacteristicsField Value
Value = 4096- Attributes
Remarks
Characteristic value signifying that the element source may be safely concurrently modified (allowing additions, replacements, and/or removals) by multiple threads without external synchronization. If so, the Spliterator is expected to have a documented policy concerning the impact of modifications during traversal.
A top-level Spliterator should not report both CONCURRENT and SIZED, since the finite size, if known, may change if the source is concurrently modified during traversal. Such a Spliterator is inconsistent and no guarantees can be made about any computation using that Spliterator. Sub-spliterators may report SIZED if the sub-split size is known and additions or removals to the source are not reflected when traversing.
A top-level Spliterator should not report both CONCURRENT and IMMUTABLE, since they are mutually exclusive. Such a Spliterator is inconsistent and no guarantees can be made about any computation using that Spliterator. Sub-spliterators may report IMMUTABLE if additions or removals to the source are not reflected when traversing.
Java documentation for java.util.Spliterator.CONCURRENT.
Portions of this page are modifications based on work created and shared by the Android Open Source Project and used according to terms described in the Creative Commons 2.5 Attribution License.