diff options
| author | Yuki Okushi <huyuumi.dev+love@gmail.com> | 2022-12-22 08:32:12 +0900 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-12-22 08:32:12 +0900 |
| commit | 4c2dd75af33db9500428e96fe0672cbcb489779a (patch) | |
| tree | 50c04cbfbb48deba7ab7200625b64924c15de673 /src/test/codegen/src-hash-algorithm/src-hash-algorithm-sha256.rs | |
| parent | 6c0dedb445db61ba47d6d07f033c19f1d7631189 (diff) | |
| parent | 30fbfd5f05108d12f08711024db699e1b0632508 (diff) | |
| download | rust-4c2dd75af33db9500428e96fe0672cbcb489779a.tar.gz rust-4c2dd75af33db9500428e96fe0672cbcb489779a.zip | |
Rollup merge of #106008 - uweigand:s390x-lintgroup-order, r=Nilstrieb
Sort lint_groups in no_lint_suggestion The no_lint_suggestion routine passes a vector of lint group names to find_best_match_for_name. That routine depends on the sort order of its input vector, which matters in case multiple inputs are at the same Levenshtein distance to the target name. However, no_lint_suggestion currently just passes lint_groups.keys() as input vector - this is sorted in hash value order, which is not guaranteed to be stable, and in fact differs between big- and little-endian host platforms, causing test failures on s390x. To fix this, always sort the lint groups before using their names as input to find_best_match_for_name. In doing so, prefer non- deprecated lint group names over deprecated ones, and then use alphabetical order. Fixes https://github.com/rust-lang/rust/issues/105379
Diffstat (limited to 'src/test/codegen/src-hash-algorithm/src-hash-algorithm-sha256.rs')
0 files changed, 0 insertions, 0 deletions