Closed zhongwencool closed 1 month ago
:wave:
Thanks for your input!
of course it is! I just means we got to put in the work and it's not currently on a 1.0 release mule stone. :)
I mean to a degree and we got to see what we're talking about here.
For the unnecessary white space between the columns, definitely. That's something I want to do in the fashion of first having it all in a map like structure - determining the widest element in a column and then adjusting the length of all others accordingly.
As for mixing memory and the comparison together into the first table, I'm not a fan of that. If memory measurements are different we need to display way more values. Also, they are quite different beasts imo. We could also have no runtime measurements and only memory measurements etc.
As for comparison, now that I think about that we could just add a column with the comparison that might be nice. However, I'm a bit wary of the space we take up. I'm not sure if taking up all of 141 is the right call. E.g. I often split my monitor half/half and would still want it to work. The comparison is mainly the way it is because I got it from benchmark-ips.
However, if any of these totally annoy you writing a custom formatter that does it like this is also totally in the cards and encouraged. Just wait for the 0.14.0 release or master after #242 has dropped.
I think the
Benchee.Formatters.Console.output/1
's output waste of space.Is it possible to make it more compact ? such as:
PS: 13-inch screen's columns is
141
.