-
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
rustdoc: correctly render the return type of cross-crate async fns #116084
Conversation
(rustbot has picked a reviewer for you, use r? to override) |
6c9d795
to
386f401
Compare
Some changes occurred in src/librustdoc/clean/types.rs cc @camelid |
386f401
to
025a2cd
Compare
Looks all good to me now, thanks! r=me once CI pass |
@bors r=GuillaumeGomez |
🌲 The tree is currently closed for pull requests below priority 100. This pull request will be tested once the tree is reopened. |
☀️ Test successful - checks-actions |
Finished benchmarking commit (0288f2e): comparison URL. Overall result: ❌ regressions - ACTION NEEDEDNext Steps: If you can justify the regressions found in this perf run, please indicate this with @rustbot label: +perf-regression Instruction countThis is a highly reliable metric that was used to determine the overall result at the top of this comment.
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: 630.479s -> 632.544s (0.33%) |
Huh weird I did not expect a perf regression. |
@fmease @GuillaumeGomez would it be possible to try not to clone? The perf regression here is large enough to make it hard to ignore. |
I'm gonna look into the regression |
@fmease: Don't hesitate to ask if you need some help |
…ession, r=<try> [perf] rustdoc: investigate recent perf regression Investigate perf regression caused by rust-lang#116084. r? `@ghost`
…ession, r=<try> [perf] rustdoc: investigate recent perf regression Investigate perf regression caused by rust-lang#116084. r? `@ghost`
…ession, r=<try> [perf] rustdoc: investigate recent perf regression Investigate perf regression caused by rust-lang#116084. r? `@ghost`
#116195 should almost entirely fix the perf regressions introduced in this PR if I read things right. |
…ession, r=GuillaumeGomez rustdoc: speed up processing of cross-crate fns to fix a perf regression * The first commit doesn't affect perf but get's rid of a `.clone()` and a bunch of lines of code. I can drop it if you'd like me to * The second commit, *“reduce the amount of `asyncness` query executions”*, addresses the perf regression introduced in rust-lang#116084 r? `@ghost`
Fixes #115760.