diff options
| author | Jacob Pratt <jacob@jhpratt.dev> | 2025-08-20 00:45:51 -0400 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-08-20 00:45:51 -0400 |
| commit | a6d648fe7907dced3fb69436b60c2ebd61d0b934 (patch) | |
| tree | 0386dc16e6dfa5691dbd61740745477945f960fa /src/librustdoc/html/static/js/scrape-examples.js | |
| parent | f605b57042ffeb320d7ae44490113a827139b766 (diff) | |
| parent | 36d309e7b98fedac1dd1905c5251299efe5f624b (diff) | |
| download | rust-a6d648fe7907dced3fb69436b60c2ebd61d0b934.tar.gz rust-a6d648fe7907dced3fb69436b60c2ebd61d0b934.zip | |
Rollup merge of #139357 - miried:master, r=Amanieu
Fix parameter order for `_by()` variants of `min` / `max`/ `minmax` in `std::cmp` We saw a regression introduced in version `1.86` that seems to be coming from switching the order of `v1` and `v2` when calling `comparison` functions in `min_by` / `max_by` / `minmax_by` (cf. this PR: https://github.com/rust-lang/rust/pull/136307) When the `compare` function 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.
Diffstat (limited to 'src/librustdoc/html/static/js/scrape-examples.js')
0 files changed, 0 insertions, 0 deletions