Closed JamesCohen-awin closed 9 years ago
I need to comb through the actual code, but it looks like it could use a little go fmt
in the meantime.
Thanks for all these contributions @JamesCohen-awin
Thanks - didn't know about go fmt
rebased to current HEAD 1ac36f2
@JamesCohen-awin thanks again, this looks good functionally - just had a few style/go idiom nitpicks
Thanks - all of the suggestions made perfect sense
give me a sec and I'll squash all of this down into a single commit
I can't fix/squash/push fast enough ;)
Going to wait until you're done and re-push
P.S. in the future you don't have to squash as we're going through code review... What we normally do is wait for a PR to get to a "LGTM" stage and then squash.
Not only is this an easier back-and-forth, but it allows the reviewer to see the changes as individual commits as they're happening, rather than losing context.
and I think I got everything now :grin:
All sorted and thanks for the education
edit: just saw the bit about the LGTM too. Noted for next time.
awesome, nice work and thanks again for all your contributions!
The etsy statsd implementation includes support for relative operations on gauges (see https://github.com/etsy/statsd/blob/master/docs/metric_types.md#gauges). I've attempted to duplicate this functionality.
I followed the statsd specs and retained the gauges as uint64 values.
This is my first attempt at coding in Go. Please be gentle!