-
-
Notifications
You must be signed in to change notification settings - Fork 358
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
Allow picking sort order of the output #614
Comments
Thank you for your request. Adding a generic sort order argument that affects both the terminal output as well as the exported markdown (and other formats?) sounds like a good idea to me! We could potentially still use different default sort orders for the terminal and the markdown, but that might be confusing because with this new option, they could not be changed independently (?). |
I think that people wanting to have different sort orders per output type is going to be very rare unless you open up some sort of reporting extension API. However, if you want to future proof things, you could do something similar to what I have in Catch2. Catch2 is a testing framework and allows multiple different reporters to be active, so I support both a generic (I picked |
Yes, agreed. Let's just add a single global sort order option.
Ohhh, you maintain Catch2. I love it 👍 |
This is now supported in https://github.com/sharkdp/hyperfine/releases/tag/v1.17.0 The output format changes completely if you use |
When I run
hyperfine --parameter-scan version 0 9 './some-command-{version}
, I get the results sorted by their speed. This can be often useful, which is why I believe it became the default, but I am specifically iterating over 10 different versions to get time series data, so I want the output in order.I did this by asking for markdown output, which is in-order, but people also request that to be sorted by speed (#603, #601). Meanwhile, I want the default output sorted by command order...
I think the solution is to make the sort order customizable for all outputs.
The text was updated successfully, but these errors were encountered: