diff options
| author | Matthias Krüger <matthias.krueger@famsik.de> | 2023-03-08 21:24:51 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-03-08 21:24:51 +0100 |
| commit | f6b8a9f6dbfad6dc0e7651cbb5372ac8f5b593c6 (patch) | |
| tree | e94262c0badd9a0f44da84a96123d437c26eadf4 /compiler/rustc_hir_analysis/src/structured_errors.rs | |
| parent | 1a9376dc47860ca4bbd21e2b5bb8fb64bba81af0 (diff) | |
| parent | 8a99ffc3442329d2fb2f07ce87852c3e12cc4d6a (diff) | |
| download | rust-f6b8a9f6dbfad6dc0e7651cbb5372ac8f5b593c6.tar.gz rust-f6b8a9f6dbfad6dc0e7651cbb5372ac8f5b593c6.zip | |
Rollup merge of #108883 - compiler-errors:post-norm-copy-err, r=BoxyUwU
Suppress copy impl error when post-normalized type references errors Suppress spurious errors from the `Copy` impl validity check when fields have bad types *post*-normalization, instead of just pre-normalization. ---- The const-generics test regressed recently due to #107965, cc `````@BoxyUwU.````` * I think it's because `[_; 0u32]: Copy` now fails to hold because a nested obligation `ConstArgHasType(0u32, usize)` fails. * It's interesting that `[const_error]` shows up in the type only after normalization, though, but I'm pretty sure that it's due to the evaluate call that happens when normalizing unevaluated consts.
Diffstat (limited to 'compiler/rustc_hir_analysis/src/structured_errors.rs')
0 files changed, 0 insertions, 0 deletions