diff options
| author | Matthias Krüger <matthias.krueger@famsik.de> | 2023-05-23 19:53:41 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-05-23 19:53:41 +0200 |
| commit | 221039b416080319cd805ede73fc7968d33a5cbd (patch) | |
| tree | 2344c26fb9e871fef5f339dc89a81d3332c38e0c /tests/rustdoc-ui/coverage/enum-tuple.rs | |
| parent | d1e9910abf8cfc67ec4acc08cef21b871eaab842 (diff) | |
| parent | 778abc7a00dff4271b48a5cd0fa256b9c28965f3 (diff) | |
| download | rust-221039b416080319cd805ede73fc7968d33a5cbd.tar.gz rust-221039b416080319cd805ede73fc7968d33a5cbd.zip | |
Rollup merge of #111486 - fmease:pp-inh-proj, r=petrochenkov
Pretty-print inherent projections correctly Previously, we were trying to pretty-print inherent projections with `Printer::print_def_path` which is incorrect since it expects the substitutions to be of a certain format (parents substs followed by own substs) which doesn't hold for inherent projections (self type subst followed by own substs). Now we print inherent projections manually. Fixes #111390. Fixes #111397. Lacking tests! Is there a test suite / compiletest flags for the pretty-printer? In most if not all cases, inherent projections are normalized away before they get the chance to appear in diagnostics. If I were to create regression tests for linked issues, they would need to be `mir-opt` tests to exercise `-Zdump-mir=all` (right?) which doesn't feel quite adequate to me. `@rustbot` label F-inherent_associated_types
Diffstat (limited to 'tests/rustdoc-ui/coverage/enum-tuple.rs')
0 files changed, 0 insertions, 0 deletions