-
Notifications
You must be signed in to change notification settings - Fork 13.2k
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
Migrate item_proc_macro
to Askama
#112031
Conversation
(rustbot has picked a reviewer for you, use r? to override) |
it: &clean::Item, | ||
m: &clean::ProcMacro, | ||
) { | ||
let mut buffer = Buffer::new(); |
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.
Just passing by on some changes happening around :)
Wondering, does the usage of Buffer
here costs us some extra allocations? I believe we can use display_fn()
to reduce that (?)
CMIIW @GuillaumeGomez
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.
This are some of my initial contributions to the compiler : )
I was thinking might not be a straightforward replacement in this case, as you'd need to handle the different MacroKind
cases inside the provided function, which could make the code a bit more complex. Also, it would require changing wrap_item function
, since we are passing a closure that modifies a buffer.
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.
Well, simplest answer: let's run perf check on this PR. :)
@bors try @rust-timer queue |
This comment has been minimized.
This comment has been minimized.
⌛ Trying commit 5c780d9 with merge 73fbdc842eb23e6820d7f013f2aa8fc4f280ce25... |
☀️ Try build successful - checks-actions |
This comment has been minimized.
This comment has been minimized.
I would be curious to know how to read the perf-test result. So that I can read them in the future. Do let me know what metrics are considered , would love to learn : ) |
Finished benchmarking commit (73fbdc842eb23e6820d7f013f2aa8fc4f280ce25): 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: 643.081s -> 643.751s (0.10%) |
…llaumeGomez Migrate `item_proc_macro` to Askama This PR migrates `item_proc_macro` to Askama Refers rust-lang#108868
…iaskrgr Rollup of 7 pull requests Successful merges: - rust-lang#112031 (Migrate `item_proc_macro` to Askama) - rust-lang#112053 (Remove `-Zcgu-partitioning-strategy`.) - rust-lang#112069 (offset_of: don't require type to be `Sized`) - rust-lang#112084 (enhancements on build_helper utilization and rustdoc-gui-test) - rust-lang#112096 (Remove array_zip) - rust-lang#112108 (Fix re-export of doc hidden item inside private item not displayed) - rust-lang#112113 (rustdoc: simplify `clean` by removing `FnRetTy`) r? `@ghost` `@rustbot` modify labels: rollup
This PR migrates
item_proc_macro
to AskamaRefers #108868