Is there any difference in why the same two orders appear in the Bug::cocos V3.2 rendering class? Hand mistake?? ----Beware of pitfalls in open source code

{    //Don ' t sort _queue0, it already comes sorted    Std::sort (Std::begin (_queuenegz), Std::end (_queuenegz), Comparerendercommand);    Std::sort (Std::begin (_queueposz), Std::end (_queueposz), Comparerendercommand);}

helperstatic bool Comparerendercommand (rendercommand* A, rendercommand* b) {    return A->getglobalorder () < B->getglobalorder ();}

Sorting does not perform other actions, is it wrong hand?


But the problem also occurs in the V3.3 RC version

This is the order of rendering commands, the purpose is generally the optimization of performance, what is the intention? Ask for explanations

Then I commented out one of the sentences and the result was correct.

The last time I found the main loop, I liked to use inefficient loops:

For (auto &renderqueue: _rendergroups)
{
Renderqueue.sort ();
}

This time to find such a pit daddy code. Readability is not bad, but a lot of small problems, really want to commercial use also need to work hard to clean up the room.

Is there any difference in why the same two orders appear in the Bug::cocos V3.2 rendering class? Hand mistake?? ----Beware of pitfalls in open source code