Ayush Chandekar <ayu.chandekar@xxxxxxxxx> writes: >> Hmph. If the implementation is correct (which I cannot tell), this >> needs to explain why it is a bit better than saying nothing. > While going through the code, I noticed the TODO comment: "Measure > QSORT() progress", and I thought it might be interesting to explore. > For big codebases, being stuck at zero would make it feel like there's > no progress happening and that is why putting a progress might be > better. That much I already know---otherwise we would not have that comment there ;-) What I meant was that the proposed log message did not give readers any hint how the implementation given in the patch is correct, the assumption it makes on the behaviour of sort(3), etc.
