diff options
| author | Matthias Krüger <matthias.krueger@famsik.de> | 2023-05-27 00:24:01 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-05-27 00:24:01 +0200 |
| commit | a99209738eedbdd80e7fd4df244eb62f046260cd (patch) | |
| tree | 9cab6819d78ffb21e704dbf9e7a75574784398a4 /compiler/rustc_mir_transform/src/coverage/query.rs | |
| parent | dfdbf1b1333a920bd5ca25f47fbedea82df33b3e (diff) | |
| parent | ad77bc8427cb181a4f0e61ba0f85c793139f9512 (diff) | |
| download | rust-a99209738eedbdd80e7fd4df244eb62f046260cd.tar.gz rust-a99209738eedbdd80e7fd4df244eb62f046260cd.zip | |
Rollup merge of #111991 - BoxyUwU:change_error_term_display, r=compiler-errors
Change ty and const error's pretty printing to be in braces
`[const error]` and `[type error]` are slightly confusing since they look like either a slice with an error type for the element ty or a slice with a const argument as the type ???. This PR changes them to display as `{const error}` and `{type error}` similar to `{integer}`.
This does not update the `Debug` impls for them which is done in #111988.
I updated some error logic to avoid printing the substs of trait refs when unable to resolve an assoc item for them, this avoids emitting errors with `{type error}` in them. The substs are not relevant for these errors since we don't take into account the substs when resolving the assoc item.
r? ``@compiler-errors``
Diffstat (limited to 'compiler/rustc_mir_transform/src/coverage/query.rs')
0 files changed, 0 insertions, 0 deletions