-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Only add non local items to RustdocEffectiveVisibilities::extern_public
#116579
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
Only add non local items to RustdocEffectiveVisibilities::extern_public
#116579
Conversation
@bors try @rust-timer queue |
This comment has been minimized.
This comment has been minimized.
…list, r=<try> Only add non local items to `RustdocEffectiveVisibilities::extern_public` While working on rust-lang#115480, I was finally able to track down the origin of the bug, still working on the fix (how to determine if a foreign trait is publically exported from the current crate in short), which led me to this small PR. It should only list foreign items and yet we don't check if they're locals before adding them to the map. I expect a very minimal perf improvement. r? `@notriddle`
☀️ Try build successful - checks-actions |
This comment has been minimized.
This comment has been minimized.
Finished benchmarking commit (aa06a90): comparison URL. Overall result: no relevant changes - no action neededBenchmarking 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. @bors rollup=never 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.
CyclesResultsThis 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.
Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 627.383s -> 625.907s (-0.24%) |
There was no significant change in perf at all, but since the data structure is supposed to only contain external public reexports, this seems better anyway. @bors r+ rollup |
How is this possible? |
@bors r- |
I might have indeed. The fact that there is no perf change is proof of that. Good catch @petrochenkov ! |
While working on #115480, I was finally able to track down the origin of the bug, still working on the fix (how to determine if a foreign trait is publically exported from the current crate in short), which led me to this small PR. It should only list foreign items and yet we don't check if they're locals before adding them to the map.
I expect a very minimal perf improvement.
r? @notriddle