rust/tests/ui/methods/probe-error-on-infinite-deref.rs

//@ compile-flags: -Zwrite-long-types-to-disk=yes
use std::ops::Deref;

// Make sure that method probe error reporting doesn't get too tangled up
// on this infinite deref impl. See #130224.

struct Wrap<T>(T);
impl<T> Deref for Wrap<T> {
    type Target = Wrap<Wrap<T>>;
    fn deref(&self) -> &Wrap<Wrap<T>> { todo!() }
}

fn main() {
    Wrap(1).lmao();
    //~^ ERROR reached the recursion limit
    //~| ERROR no method named `lmao`
}
Use `tcx.short_string()` in more diagnostics `TyCtxt::short_string` ensures that user visible type paths aren't overwhelming on the terminal output, and properly saves the long name to disk as a side-channel. We already use these throughout the compiler and have been using them as needed when users find cases where the output is verbose. This is a proactive search of some cases to use `short_string`. We add support for shortening the path of "trait path only". Every manual use of `short_string` is a bright marker that that error should be using structured diagnostics instead (as they have proper handling of long types without the maintainer having to think abou tthem). When we don't actually print out a shortened type we don't need the "use `--verbose`" note. On E0599 show type identity to avoid expanding the receiver's generic parameters. Unify wording on `long_ty_path` everywhere. 2025-07-16 19:45:07 +00:00			`//@ compile-flags: -Zwrite-long-types-to-disk=yes`
Do not report an excessive number of overflow errors for an ever-growing deref impl 2024-09-12 14:32:55 -04:00			`use std::ops::Deref;`

			`// Make sure that method probe error reporting doesn't get too tangled up`
			`// on this infinite deref impl. See #130224.`

			`struct Wrap<T>(T);`
			`impl<T> Deref for Wrap<T> {`
			`type Target = Wrap<Wrap<T>>;`
			`fn deref(&self) -> &Wrap<Wrap<T>> { todo!() }`
			`}`

			`fn main() {`
			`Wrap(1).lmao();`
			`//~^ ERROR reached the recursion limit`
			//~\| ERROR no method named `lmao`
			`}`