Fix parameter order for _by() variants of min / max/ minmax in std::cmp#139357
Merged
bors merged 3 commits intorust-lang:masterfrom Aug 20, 2025
Merged
Fix parameter order for _by() variants of min / max/ minmax in std::cmp#139357bors merged 3 commits intorust-lang:masterfrom
_by() variants of min / max/ minmax in std::cmp#139357bors merged 3 commits intorust-lang:masterfrom
Conversation
Loading
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
10 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
We saw a regression introduced in version
1.86that seems to be coming from switching the order ofv1andv2when callingcomparisonfunctions inmin_by/max_by/minmax_by(cf. this PR: #136307)When the
comparefunction is not symmetric in the arguments, this leads to false results. Apparently, the test cases do not cover this scenario currently. While asymmetric comparison may be an edge case, but current behavior is unexpected nevertheless.