Chris A.

Going to need it later for differential/catch-up migrations. I could elide via a wrapper but I am hellaciously lazy. Thanks for the heads up. :) I'll close this as fixed...

+1 I have the same problem on OS X.

Where'd your website go? http://vitalreactor.com/

If I buy you a six-pack, will you rename the libraries prefixed with "clj-*" in your GitHub?

@mcasper I'll try to make the `cfg` flagging behave along the lines you've suggested here. I don't know if your description was inclusive of this or not but I'd like...

> I suppose we could try to change the API away from "convenience function for every stat" to something like "build the stat struct yourself and then use the correct...

First note, I'm using stable so I can't have a feature named the same thing as a crate (`tokio`) because only nightly has namespacing like `dep:tokio`. I named the feature...

I've been using this library in production to emit about 30 billion events per month, however, I've been doing so with a synchronous client because the UDP interface ended up...

I've got a PR up for a Tokio client here: https://github.com/mcasper/dogstatsd-rs/pull/33

Fails for me too. GHC: 7.6.3 cabal: 1.18.0.2 I was using cabal sandbox.