rust/tests/ui/methods/call_method_unknown_referent.stderr
Esteban Küber 99196657fc 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-08-07 21:18:00 +00:00

30 lines
1.1 KiB
Plaintext

error[E0282]: type annotations needed
--> $DIR/call_method_unknown_referent.rs:20:31
|
LL | let _a: i32 = (ptr as &_).read();
| ^^^^ cannot infer type
error[E0282]: type annotations needed
--> $DIR/call_method_unknown_referent.rs:26:37
|
LL | let _b = (rc as std::rc::Rc<_>).read();
| ^^^^ cannot infer type
error[E0599]: no method named `read` found for struct `SmartPtr<T>` in the current scope
--> $DIR/call_method_unknown_referent.rs:46:35
|
LL | struct SmartPtr<T>(T);
| ------------------ method `read` not found for this struct
...
LL | let _c = (ptr as SmartPtr<_>).read();
| ^^^^ method not found in `SmartPtr<_>`
|
= help: items from traits can only be used if the trait is implemented and in scope
= note: the following trait defines an item `read`, perhaps you need to implement it:
candidate #1: `std::io::Read`
error: aborting due to 3 previous errors
Some errors have detailed explanations: E0282, E0599.
For more information about an error, try `rustc --explain E0282`.