In this article you can find how to create custom method of sorting strings in C#.
For the beginning let’s create an example list of strings, which are compass directions in random order.
When we iterate through the collection using foreach loop and print items to the console, we should see the same order as above.
Indeed, the output is as expected.
Time to sort something. We can achieve it in different ways, however in this article I’d like to show two most popular.
1. List<T>.Sort();
Sort method is available against List objects and by default, in case of strings, it sorts those in alphabetical order. In the background it uses Quicksort algorithm and this implementation is considered as unstable. It means it’s not guaranteed two the same elements will preserve the same order after sorting as it was before. It may not make any difference when sorting just strings, however may be important when sorting lists of other, more complex objects.
Let’s sort our prepared list using below code. Please notice Sort function doesn’t return anything and just alters the original collection, therefore we lose the initial order.
After printing it to screen again, using the same loop as before we can see items in alphabetical order.
So far, so good, but now we’d like to sort the collection slightly different. Still in alphabetical order, however starting comparison from the end of each string, not the beginning as usual. To achieve it we need to implement custom algorithm, because built-in method doesn’t provide such functionality.
Again, we have a choice. When we look closer to the Sort function, we can see it’s overloaded. I’d like to focus on two options: Comparison<string> comparison and IComparer<string> comparer.
1.a. Comparison<string> comparison
Comparison is delegate type declared as you can see below, which receives two arguments of the same type (string in our case) and returns integer.
As a result of above we need to create our custom comparison method which has two string arguments and returns int. It’ll be used by sorting algorithm to compare pairs of two strings.
The method uses built-in CompareTo, which returns 0 when items are equal and either -1 or 1 when items are not equal. Existence of minus depends whether value1 should be before value2 or the other way. We also need function to temporary reverse the values (e.g. abc to cba).
This is it. Now we can replace previous call of Sort with the new one.
After above changes the output is totally different, but directions are sorted as we expected, so our custom comparison function works fine.
And full scope is here.
1.b. IComparer<string> comparer
Second option is to create a class implementing IComparer<T> interface, which contains Compare method.
Let’s implement it, using the same logic as previously.
This time we need to pass to Sort function an instance of our ReversedComparer class.
Rebuild, run, and the output is correct again. Directions are sorted with our custom comparer.
And full scope is here.
2. List<T>.OrderBy()
OrderBy method is an element of LINQ and the same as Sort, by default it sorts strings in alphabetical order. In the background it also uses Quicksort algorithm however it implements additional mechanism which checks the initial order when two comparing keys are equal. As the result of what that implementation can be considered as stable. The other difference between Sort and OrderBy is not changing original collection. OrderBy returns ordered items as new object type IOrderedEnumerable<T>, so after sorting to work with newly ordered items you need to use either the new object or assign the returned value to the original object.
Let’s then sort. As you can see below, statement is slightly more complicated than earlier but still very easy. Firstly, OrderBy doesn’t have implementation which not takes any arguments. We need to pass at least one which defines the key which is used to sort. Our collection contains just strings, so we can easily define the key using simple lambda expression x => x. Secondly, we’d like to assign ordered collection to the original one and still use the same object called directions. To do so, we need to convert result of OrderBy which in our case is IOrderedEnumerable<string> to list with ToList function.
The result is predictable, which is list of our directions in alphabetical order.
Now it’s time to make OrderBy working with our custom algorithm. Again we’d like to sort strings in alphabetical order starting comparison from the end of those strings and not as default from beginning.
2.a. IComparer<string> comparer
OrderBy function is overloaded and there is a variant with two input arguments. First is key selector as previously and second one is argument which accepts objects implementing IComparer<T>. As you can see it’s exactly the same option as the one on Sort function. As we already implemented comparer class, let’s reuse it here.
In the result we can see sorted collection with our custom algorithm.
And full scope is here.
Summary
To sum up I hope you find this article useful. The example used here of sort algorithm is very simple, however it was intention just for training purposes. In your application you can implement much more complex methods depending on your needs.