tree 5b60eac9a0b835860182e8b05d2aeffc51298786
parent 1dd567da00eec3ccfbcbafb7a04f4297e7a69b48
author Austin Clements <austin@google.com> 1634745019 -0400
committer Austin Clements <austin@google.com> 1730225290 +0000

14313-benchmark-format: add unit metadata

The predefined keys differ slightly from what I proposed in golang/go#43744. I
tried specifying {higher,lower}={better,worse} like I originally
proposed and it just got really messy. Turning it around to
better={higher,lower} means its somewhat backwards from what you might
expect from English phrasing, but it lets us use a single key because
I don't think anyone is going to accidentally write
worse={higher,lower}, and this avoids any annoying questions about
what happens if a user specifies both "higher" and "lower".

For golang/go#43744.

Change-Id: I895914b179c291003e76f897cabbcbdb2381f163
Reviewed-on: https://go-review.googlesource.com/c/proposal/+/357530
Reviewed-by: Michael Knyszek <mknyszek@google.com>