-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
Refactoring report_method_error #105752
Refactoring report_method_error #105752
Conversation
0da20a8
to
bda60d6
Compare
☔ The latest upstream changes (presumably #105746) made this pull request unmergeable. Please resolve the merge conflicts. |
This could use a rebase. I'll approve after that. |
bda60d6
to
e686eb3
Compare
@rustbot ready |
☔ The latest upstream changes (presumably #84762) made this pull request unmergeable. Please resolve the merge conflicts. |
e686eb3
to
93e62a4
Compare
emmm, conflict again... |
@bors r+ |
☀️ Test successful - checks-actions |
Finished benchmarking commit (c757267): comparison URL. Overall result: no relevant changes - no action needed@rustbot label: -perf-regression Instruction countThis benchmark run did not return any relevant results for this metric. Max RSS (memory usage)ResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
CyclesThis benchmark run did not return any relevant results for this metric. |
While working on #105732, I found it's hard to follow this long function,
so I tried to make it shorter.
It's not easy for code reviewing, since so many lines of code changes,
but only the positions are changed.
Generally, I extract two sub-methods from
report_method_error
:rust/compiler/rustc_hir_typeck/src/method/suggest.rs
Line 117 in 397b66e
to
note_candidates_on_method_error
And this long block:
rust/compiler/rustc_hir_typeck/src/method/suggest.rs
Line 263 in 397b66e
to
report_no_match_method_error
.r? @compiler-errors