-
Notifications
You must be signed in to change notification settings - Fork 13.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Check namespaces when resolving associated items in typeck #45297
Check namespaces when resolving associated items in typeck #45297
Conversation
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @pnkfelix (or someone else) soon. If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes. Please see the contribution instructions for more information. |
}) | ||
.collect() | ||
} else { | ||
self.fcx.associated_item(def_id, name).map_or(Vec::new(), |x| vec![x]) | ||
self.fcx.associated_item(def_id, name, Namespace::Value).map_or(Vec::new(), |x| vec![x]) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This line is too long.
[00:03:58] tidy error: /checkout/src/librustc_typeck/check/method/probe.rs:1326: line longer than 100 chars
cf71357
to
9845e09
Compare
9845e09
to
3f30f9e
Compare
3f30f9e
to
b522ee1
Compare
This is great, two less issues on my backlog! :) |
📌 Commit b522ee1 has been approved by |
☀️ Test successful - status-appveyor, status-travis |
Closes #35600
Closes #44247
Fixes a "cannot move a value of type..." error in the same case as #44247 but with the associated items swapped.