returned for Tags:"ConcurrentQueue"
Observable Concurrent Queue based on the classic concurrent queue (System.Collections.Concurrent.ConcurrentQueue) Allows to raise events when the queue content is changed with the same events as ObservableCollection
Why is it that the List is so widely used, even when there is absolutly no need for the features of a List? I think one of the most important reasons is it beeing so easily available. You could simply use the extension method .ToList() on any IEnumerable.
To help out in this matter, and hopefully...
This is a .NET Standard 1.0, Silverlight 5.0 and Windows Phone Silverlight 8.0 & 8.1 backport from System.Collections.Concurrent.ConcurrentDictionary and System.Collections.Concurrent.ConcurrentQueue as defined in .NET Core
C# Engine to download multiple WebRequests in Paralel with TLP and Concurrent Blocking COllection
Extensions to transform IEnumerable into other generic collection types, including async versions.