diff options
| author | Matthias Krüger <matthias.krueger@famsik.de> | 2024-09-23 06:45:36 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-09-23 06:45:36 +0200 |
| commit | 2bca5c4fc1a27a7913dd4d7eb5bc98cc84977d17 (patch) | |
| tree | 4eaa55bbdb1f5a73daa71d28578c755066ab8c62 /compiler/rustc_pattern_analysis | |
| parent | 8bb69b1861bae75fe015bb2b12a4ab1751de0101 (diff) | |
| parent | 3b8089a32055fe9b716db3fcd9d61ccc5bfed97b (diff) | |
| download | rust-2bca5c4fc1a27a7913dd4d7eb5bc98cc84977d17.tar.gz rust-2bca5c4fc1a27a7913dd4d7eb5bc98cc84977d17.zip | |
Rollup merge of #130714 - compiler-errors:try-structurally-resolve-const, r=BoxyUwU
Introduce `structurally_normalize_const`, use it in `rustc_hir_typeck` Introduces `structurally_normalize_const` to typecking to separate the "eval a const" step from the "try to turn a valtree into a target usize" in HIR typeck, where we may still have infer vars and stuff around. I also changed `check_expr_repeat` to move a double evaluation of a const into a single one. I'll leave inline comments. r? ```@BoxyUwU``` I hesitated to really test this on the new solver where it probably matters for unevaluated consts. If you're worried about the side-effects, I'd be happy to craft some more tests 😄
Diffstat (limited to 'compiler/rustc_pattern_analysis')
0 files changed, 0 insertions, 0 deletions