Cycle sort is an in-place, unstable sorting algorithm, a comparison sort that is theoretically optimal in terms of the total number of writes to the original array, unlike any other in-place sorting algorithm. It is based on the idea that the permutation to be sorted can be factored into cycles, which can individually be rotated to give a sorted result. Unlike nearly every other sort, items are never written elsewhere in the array simply to push them out of the way of the action. Each value is either written zero times, if it's already in its correct position, or written one time to its correct position. This matches the minimal number of overwrites required for a completed in-place sort. Minimizing the number of writes is useful when making writes to some huge data set is very expensive, such as with EEPROMs like Flash memory where each write reduces the lifespan of the memory. Algorithm To illustrate the idea of cycle sort, consider a list with distinct elements. Given an element , we can find the index at which it will occur in the sorted list by simply counting the number of elements in the entire list that are smaller than . Now If the element is already at the correct position, do nothing. If it is not, we will write it to its intended position. That position is inhabited by a different element , which we then have to move to its correct position. This process of displacing elements to their correct positions continues until an element is moved to the original position of . This completes a cycle. Repeating this process for every element sorts the list, with a single writing operation if and only if an element is not already at its correct position. While computing the correct positions takes time for every single element, thus resulting in a quadratic time algorithm, the number of writing operations is minimized. Implementation To create a working implementation from the above outline, two issues need to be addressed: When computing the correct positions, we have to make sure not to double-count the first element of the cycle. If there are duplicate elements present, when we try to move an element to its correct position, that position might already be inhabited by an . Simply swapping these would cause the algorithm to cycle indefinitely. Instead, we have to insert the element after