-
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
Remove BadImplStripper code #96337
Remove BadImplStripper code #96337
Conversation
Some changes occurred in cc @camelid |
Let's check if there is an impact on perf: @bors try @rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit b178b09 with merge 2ab0cef387112435a80c2aa6f3fad22792145372... |
The job Click to see the possible cause of the failure (guessed by this bot)
|
Seems like |
☀️ Try build successful - checks-actions |
Queued 2ab0cef387112435a80c2aa6f3fad22792145372 with parent 09064a2, future comparison URL. |
Finished benchmarking commit (2ab0cef387112435a80c2aa6f3fad22792145372): comparison url. Summary:
If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. Benchmarking this pull request likely means that it is perf-sensitive, so we're automatically marking it as not fit for rolling up. While you can manually mark this PR as fit for rollup, we strongly recommend not doing so since this PR may lead to changes in compiler perf. Next Steps: If you can justify the regressions found in this try perf run, please indicate this with @bors rollup=never Footnotes |
That's quite the disaster. 😆 Oh well, now we know. :) |
@GuillaumeGomez obviously, we can't land this as-is, but I think it might still be worth investigating a modification of this PR. My recollection is that |
Following this comment suggestion. I gave a try at removing
BadImplStripper
.I ran rustdoc tests and all passed so apparently it's now possible to not rely on
BadImplStripper
anymore. Is there maybe a case that isn't covered by the tests though?r? @camelid