[codegen] Use descriptive benchmark target fn name.#3082
[codegen] Use descriptive benchmark target fn name.#3082jswrenn wants to merge 1 commit intoGed67b8f5ad7d38d9f2eb40adebea8894a1a6a008from
Conversation
gherrit-pr-id: Gff7f5c476000b38dbce1a040586076c9ff44a8d4
Summary of ChangesHello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request refactors the naming convention for benchmark functions and their associated test infrastructure. The primary goal is to improve the clarity and readability of benchmark tests by assigning more descriptive names to the functions being benchmarked. This change is consistently applied across the Rust source files, their generated assembly outputs, and the test runner, ensuring that the benchmark targets are easily identifiable and their purpose is immediately clear. Highlights
🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console. Changelog
Activity
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## Ged67b8f5ad7d38d9f2eb40adebea8894a1a6a008 #3082 +/- ##
==========================================================================
Coverage 91.87% 91.87%
==========================================================================
Files 20 20
Lines 6057 6057
==========================================================================
Hits 5565 5565
Misses 492 492 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
There was a problem hiding this comment.
Code Review
This pull request refactors the codegen benchmark tests to use descriptive function names instead of the generic codegen_test. This is achieved by updating the test runner to construct the function name from the benchmark file name. The changes are straightforward and improve the maintainability of the benchmarks. I have one suggestion to remove a debugging print statement from the test runner.
Latest Update: v5 — Compare vs v4
📚 Full Patch History
Links show the diff between the row version and the column version.
⬇️ Download this PR
Branch
git fetch origin refs/heads/Gff7f5c476000b38dbce1a040586076c9ff44a8d4 && git checkout -b pr-Gff7f5c476000b38dbce1a040586076c9ff44a8d4 FETCH_HEADCheckout
git fetch origin refs/heads/Gff7f5c476000b38dbce1a040586076c9ff44a8d4 && git checkout FETCH_HEADCherry Pick
git fetch origin refs/heads/Gff7f5c476000b38dbce1a040586076c9ff44a8d4 && git cherry-pick FETCH_HEADPull
Stacked PRs enabled by GHerrit.