about summary refs log tree commit diff
path: root/compiler/rustc_errors/src/snippet.rs
diff options
context:
space:
mode:
authorMatthias Krüger <matthias.krueger@famsik.de>2025-01-28 18:17:27 +0100
committerGitHub <noreply@github.com>2025-01-28 18:17:27 +0100
commitda49fcdbb4da3149f8dcc6868f0cb1d43da04442 (patch)
treef876392fe94ef3c22c981dde64f80297e820c1f7 /compiler/rustc_errors/src/snippet.rs
parentd43e78d6eaede16edc5cd398c102021903507d38 (diff)
parentd898aa3c334efacb64295f1dd36cfd50e0a74e9d (diff)
downloadrust-da49fcdbb4da3149f8dcc6868f0cb1d43da04442.tar.gz
rust-da49fcdbb4da3149f8dcc6868f0cb1d43da04442.zip
Rollup merge of #136124 - adetaylor:test-comment, r=compiler-errors
Arbitrary self types v2: explain test.

The purpose of this test wasn't obvious, as ```@traviscross``` noted. Add a comment.

Confession: although this test was added to demonstrate this particular corner-case, I can no longer reproduce the original problem, even if I adjust `rustc` to do the "wrong" thing. I have spent several hours trying to adjust the case to trigger the "faulty" behavior with no success. This test may therefore not be as useful as it originally was. But it still seems worthwhile retaining as a regression test that we don't break things in these quirky circumstances. Ideally we'd find a new test which tests this behavior but I've failed to come up with one.

r? ```@traviscross```
Diffstat (limited to 'compiler/rustc_errors/src/snippet.rs')
0 files changed, 0 insertions, 0 deletions