diff options
| author | 许杰友 Jieyou Xu (Joe) <39484203+jieyouxu@users.noreply.github.com> | 2025-03-05 21:46:42 +0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-03-05 21:46:42 +0800 |
| commit | 6c60abf51a179c8daafee7a706642758ec4a6b56 (patch) | |
| tree | 5f90a48c0e18c5bd026afe2c8c8cbf25ccf0c744 /compiler/rustc_codegen_llvm/src/errors.rs | |
| parent | 604d1ba61cc6768e96f0822d9480bbff8dc9b7be (diff) | |
| parent | d75995813112b0297ec727ab4de32c48adb7d695 (diff) | |
| download | rust-6c60abf51a179c8daafee7a706642758ec4a6b56.tar.gz rust-6c60abf51a179c8daafee7a706642758ec4a6b56.zip | |
Rollup merge of #137633 - compiler-errors:no-implied-bounds-hack-unless-bevy, r=lcnr
Only use implied bounds hack if bevy, and use deeply normalize in implied bounds hack Consolidates the implied bounds computation mode into a single function, which deeply normalizes, and if it's in **compat** mode (for bevy), it extracts outlives bounds from the infcx. Previously, we were using the implied bounds compat mode in two cases: 1. During WF, if it detects `ParamSet` 2. EVERYWHERE ELSE (lol) -- e.g. borrowck, predicate entailment, etc. While I think this is fine, and the net effect was just that we emitted fewer diagnostics, it makes me uncomfortable that all crates were using the supposed "compat" code. Fixes #137767
Diffstat (limited to 'compiler/rustc_codegen_llvm/src/errors.rs')
0 files changed, 0 insertions, 0 deletions