Many algorithms - for instance Dijkstra's well-known search for the shortest path - run most efficient with a 'semi-sorted' list, which always has the smallest element up front. The most efficient structure for this purpose is a heap, also called priority queue.
PriorityQueue class is built in the guidelines of the
System.Collections namespace. Comparison is done through the
IComparer interface, or, if none is specified, through the
IComparable implementation of the provided objects. The objects in the PQ need not have all the same type but they have to be comparable with each other.
Next to the standard
System.Collections methods (
Contains, ... you name it), the PQ supports 3 main operations:
Push(): This will add an object to the PQ, reforming the structure so that this element is at the front if it is the currently smallest. The complexity of the operation is O(ld n).
Pop(): This will remove and return the current head of the PQ, which always is the smallest element. Complexity O(ld n).
Update(): It might be necessary to change elements that are already in the queue. Because this is not very common (you need to find the element first), it can only be done by the explicit
IList implementation (the indexer should not be used in any other case). Once you set the indexer, the PQ will automatically reorder. Complexity O(ld n) (surprise;))
IPriorityQueue PQ = new BinaryPriorityQueue();
Random R = new Random();
I did my diploma in Dresden and Sydney where I dealt with algorithms, agents and other cool AI stuff. Now I moved to Frankfurt to work on my PhD dealing with software structures for artificial intelligence systems. If I can, I do things in C# and ASP.NET, but if I have to, my C++, Java and SQL are not that bad.
Long Live .NET.