-
Notifications
You must be signed in to change notification settings - Fork 13k
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
rustdoc: Remove fields_stripped fields (and equivalents) #94053
Conversation
rustdoc-json-types is a public (although nightly-only) API. If possible, consider changing cc @CraftSpider,@aDotInTheVoid Some changes occurred in cc @camelid |
@bors try @rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit a2c2a87a8a969bff68913fe5e19b03e09fa49cac with merge 4360c1576eea23a5bff62ffa26427cf63e1a0bd5... |
☀️ Try build successful - checks-actions |
Queued 4360c1576eea23a5bff62ffa26427cf63e1a0bd5 with parent a240ccd, future comparison URL. |
Finished benchmarking commit (4360c1576eea23a5bff62ffa26427cf63e1a0bd5): comparison url. Summary: This benchmark run did not return any relevant results. 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 led to changes in compiler perf. @bors rollup=never |
a2c2a87
to
e3b32dd
Compare
Seems like there is close to no perf improvement. Well, that's always one field less to worry about. :) |
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.
Thanks for doing this, I left some comments.
☔ The latest upstream changes (presumably #94733) made this pull request unmergeable. Please resolve the merge conflicts. |
ping @GuillaumeGomez :) |
In my TODO list. :) |
e3b32dd
to
a8f3f86
Compare
36c22b7
to
29d6770
Compare
Finally took the time to update it! The remaining problem was that |
☔ The latest upstream changes (presumably #97239) made this pull request unmergeable. Please resolve the merge conflicts. |
29d6770
to
d803cae
Compare
Fixed the merged conflict. Since @camelid is busy, I'll set someone else as reviewer. r? @notriddle |
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.
Should probably write down what we learned somewhere.
Co-authored-by: Michael Howell <michael@notriddle.com>
I directly added your suggestion because there is nothing for me to change or add. :) |
@bors r+ rollup=never |
@bors r+ rollup=never |
📌 Commit 8323b05 has been approved by |
☀️ Test successful - checks-actions |
Finished benchmarking commit (222c572): comparison url. Instruction countThis benchmark run did not return any relevant results for this metric. Max RSS (memory usage)Results
CyclesResults
If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. @rustbot label: -perf-regression Footnotes |
Fixes #90588.
r? @camelid