I don't yet know enough about how gauges will be used to know if defaulting to 0 makes sense. Until we have a better idea, it seems safer to me to not have implicit defaulting logic.

On Sat, Mar 9, 2013 at 2:22 AM, Bernd Ahlers <notifications@github.com>
wrote:

>> @@ -0,0 +1,27 @@
>> +require 'atomic'
>> +
>> +module Metriks
>> +  class Gauge
>> +    # Public: Initialize a new Gauge.
>> +    def initialize(callable = nil, &block)
>> +      @gauge = Atomic.new(0)
> So the reporters have to handle nil values? The graphite reporter would currently write the following to graphite if the value returns `nil`.
> ```
> foo.value  1362824488
> ```
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/eric/metriks/pull/33/files#r3307711