Author: Unknown
Subject: # calls to remD()
Date: Sunday, 22 Mar 2020, 13:57:08

When I use a variable to keep track of the number of calls to remD() while sorting test file f8192 and print it at the end, it ends up being exactly the upper bound described in the specification. However, the public test tells me that I've exceeded the number of calls to remD(). Is there a way we can access the number of calls being recorded by the test file to figure out what is going wrong?