docs: document benchmark argument names#2180
Merged
dmah42 merged 1 commit intogoogle:mainfrom Apr 26, 2026
Merged
Conversation
Contributor
Author
|
@dmah42 please review |
dmah42
approved these changes
Apr 26, 2026
Collaborator
|
Thank you! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Documents how to use
ArgNameandArgNamesto make generated benchmark names easier to read when benchmarks use numeric arguments.Fixes #1661
Details
Naming Benchmark Argumentssubsection to the user guide.ArgNamefor single-argument benchmarks.ArgNamesfor benchmarks with multiple arguments.BM_SetInsert/size:100/inserts:128.