mirror of
https://github.com/rust-lang/rust.git
synced 2024-11-23 07:14:28 +00:00
f926031ea5
When we have a resolution error when looking at a fully qualified path on a type, look for all associated functions on inherent impls that return `Self` and mention them to the user. Fix #69512.
31 lines
1.0 KiB
Plaintext
31 lines
1.0 KiB
Plaintext
error[E0433]: failed to resolve: maybe a missing crate `x`?
|
|
--> $DIR/issue-82865.rs:5:5
|
|
|
|
|
LL | use x::y::z;
|
|
| ^ maybe a missing crate `x`?
|
|
|
|
|
= help: consider adding `extern crate x` to use the `x` crate
|
|
|
|
error[E0599]: no function or associated item named `z` found for struct `Box<_, _>` in the current scope
|
|
--> $DIR/issue-82865.rs:8:10
|
|
|
|
|
LL | Box::z
|
|
| ^ function or associated item not found in `Box<_, _>`
|
|
...
|
|
LL | mac!();
|
|
| ------ in this macro invocation
|
|
|
|
|
note: if you're trying to build a new `Box<_, _>` consider using one of the following associated functions:
|
|
Box::<T>::new
|
|
Box::<T>::new_uninit
|
|
Box::<T>::new_zeroed
|
|
Box::<T>::try_new
|
|
and 18 others
|
|
--> $SRC_DIR/alloc/src/boxed.rs:LL:COL
|
|
= note: this error originates in the macro `mac` (in Nightly builds, run with -Z macro-backtrace for more info)
|
|
|
|
error: aborting due to 2 previous errors
|
|
|
|
Some errors have detailed explanations: E0433, E0599.
|
|
For more information about an error, try `rustc --explain E0433`.
|