You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a general problem with paths in error messages and somewhat related to #13065.
What we should be doing is for each resolved definition of an item, find the publicly accessible path to that item. Such a path will always exist due to the restriction on exposing private types. This may or may not be a non-trivial change to resolve, though.
diagnostics: make paths to external items more visible
This PR changes the reported path for an external item so that it is visible from at least one local module (i.e. it does not use any inaccessible external modules) if possible. If the external item's crate was declared with an `extern crate`, the path is guarenteed to use the `extern crate`.
Fixes#23224, fixes#23355, fixes#26635, fixes#27165.
r? @nrc
I am too new at rust to know if this is really an issue or not.
I was trying to get the sample "guess" program to work. At one point I got this warning:
So I change my namespace to use 'core' and I got this error:
In the end, the solution was to use "std::cmp::Ordering::Less" - so the bug(?) is the warning message steering me to the wrong namespace.
The text was updated successfully, but these errors were encountered: