← Back to context Comment by readthenotes1 5 days ago I wonder how many nanoseconds it'll take for the next maintainer to obliterate the savings? 2 comments readthenotes1 Reply jasonthorsness 5 days ago For low-level small things tests can help. Go has good benchmarking built-in and you can use a tool that passes/fails based on statistically-significant regressions, benchstat (https://pkg.go.dev/golang.org/x/perf/cmd/benchstat). hu3 5 days ago That's just one prompt away!
jasonthorsness 5 days ago For low-level small things tests can help. Go has good benchmarking built-in and you can use a tool that passes/fails based on statistically-significant regressions, benchstat (https://pkg.go.dev/golang.org/x/perf/cmd/benchstat).
For low-level small things tests can help. Go has good benchmarking built-in and you can use a tool that passes/fails based on statistically-significant regressions, benchstat (https://pkg.go.dev/golang.org/x/perf/cmd/benchstat).
That's just one prompt away!