To check whether a list or any data structure for that matter is a task that only takes O(n) time. Just iterate over the list using the Iterator Interface and run through the data (in your case you already have it ready as a type of Comparable) from start to end and you can find whether its sorted or not easily
This is an operation that will take O(n) time (worst case). You will need to handle two cases: where the list is sorted in descending order, and where the list is sorted in ascending order.
You will need to compare each element with the next element while making sure that the order is preserved.
There's also the Ordering class, though this is mostly obsolete. An Ordering is a Comparator++. In this case, if you have a list of some type that implements Comparable, you could write:
This works for any Iterable, not just List, and you can handle nulls easily by specifying whether they should come before or after any other non-null elements:
Ordering.natural().nullsLast().isOrdered(list);
Also, since you mentioned that you'd like to be able to check for reverse order as well as normal, that would be done as:
public static <T extends Comparable<? super T>>
boolean isSorted(Iterable<T> iterable) {
Iterator<T> iter = iterable.iterator();
if (!iter.hasNext()) {
return true;
}
T t = iter.next();
while (iter.hasNext()) {
T t2 = iter.next();
if (t.compareTo(t2) > 0) {
return false;
}
t = t2;
}
return true;
}
public static <T extends Comparable<? super T>> boolean isSorted(T[] a, int start, int end) {
while (start<end) {
if (a[start].compareTo(a[start+1])>0) return false;
start++;
}
return true;
}
Converting for lists:
public static <T extends Comparable<? super T>> boolean isSorted(List<T> a) {
int length=a.size();
if (length<=1) return true;
int i=1;
T previous=a.get(0);
while (i<length) {
T current=a.get(i++);
if (previous.compareTo(current)>0) return false;
previous=current;
}
return true;
}
This code will sort the list out of place and collect its elements in another list, which is then compared to the initial list. The comparison will be successful, if both lists contain the same elements in equal positions.
Note that this method will have worse space and time complexity than other approaches because it will have to sort the list out of place, so it should not be used for very large lists. But it is the easiest to use because it is a single expression and does not involve 3rd party libraries.
IMO, from what I'm seeing, the complexity of checking this is as bad as performing the sort for a second time, and I understand people are short circuiting with returns if it is not sorted, but if the List is actually sorted, then the entire length will be traversed..., I'd argue to just let the code continue as if the List was sorted, and let the code itself figure out if it is or not.
I would recommend placing an Error detailing why the specific line that will fail is doing so because its collection is not reversed/ordered etc...
eg.
the line detachTailIndex.run() will give a NullPointerException(),
if (fromReversedMethod && detachTailIndex == null) {
throw new NullPointerException("detachTailIndex was null. \n
Reason: The List<> is required to be reversed before submission")
}
Or if your plan is to use a conditional for when sorted or not the you can use the null to verify if it is sorted and choose the other option.
If there is no other option, then using the other responses are ok.
Here is another example:
int key = entry.getKey();
List<Integer> shouldBeReversed = entry.getValue();
try {
//If all entries need to be iterated better place them inside the Try-Catch
updateBatch(key,
xes -> {
for (int rowIndex : shouldBeReversed
) {
xes.remove((int) rowIndex); // will return an IndexOutOfBoundsException if not sorted in reverse
}
return xes;
}
);
} catch (IndexOutOfBoundsException e) {
throw new IndexOutOfBoundsException(e.getMessage() + "\n" +
"Reason: Batch indexes (Entry's value \"List<Integer>\") should be sorted in reverse order before submission");
}
if conditional is required (on sorted, or on not sorted) then the
catch() body could be used as a "not sorted" option.
Of course this is very very case specific, but seems that checking for a sorting order just to get a boolean seems too much (?) specially on iterations.