-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
Make sure rust-call errors occur correctly for traits #79675
Conversation
r? @estebank (rust-highfive has picked a reviewer for you, use r? to override) |
@estebank are you available to review this? Apologies if you're busy |
r? @oli-obk |
@CraftSpider apologies for the delay. I spent the entirety of December offline, which is why I didn't review this (and the triaging team doesn't pick these up earlier because some weeks have to pass before then). Looking at this now. |
📌 Commit d41122a has been approved by |
Also, wg-triage is on break until next week :) |
Rollup of 7 pull requests Successful merges: - rust-lang#79675 (Make sure rust-call errors occur correctly for traits) - rust-lang#80372 (Don't panic when an external crate can't be resolved) - rust-lang#80761 (handle generic trait methods in coverage-report tests) - rust-lang#80785 (rustc_ast_pretty: Remove `PrintState::insert_extra_parens`) - rust-lang#80791 (Fix type name in doc example for Iter and IterMut) - rust-lang#80794 (Use Option::map_or instead of `.map(..).unwrap_or(..)`) - rust-lang#80799 (Get rid of custom pretty-printing in rustdoc) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
beta backport has been declined. Zulip discussion from the compiler team at this link. |
Fixes #79669
Adds trait method resolution to the error, and adds UI tests to ensure it doesn't happen again. Opening as draft because I'm getting weird link errors from unrelated code on my machine, and want to see what CI thinks.