class BigDecimal

:nodoc:
it still has the chance to post-process the string and get the real value.
the other end knows by contract that the data is supposed to be a BigDecimal,
That's why a JSON string is returned. The JSON literal is not numeric, but if

other than manually inspecting the string with the JSON code itself.
those libraries would get in general a wrong number and no way to recover
however, parse non-integer JSON numbers directly as floats. Clients using
A BigDecimal would be naturally represented as a JSON number. Most libraries,

def as_json(options = nil) to_s end #:nodoc:

def duplicable?
  true
end

def encode_with(coder)
  string = to_s
  coder.represent_scalar(nil, YAML_MAPPING[string] || string)
end

def to_d
  self
end

def to_formatted_s(format = DEFAULT_STRING_FORMAT)
  _original_to_s(format)
end

Note that reconstituting YAML floats to native floats may lose precision.

This is better than self.to_f.to_s since it doesn't lose precision.
This emits the number without any scientific notation.

def to_yaml(opts = {})
  return super if defined?(YAML::ENGINE) && !YAML::ENGINE.syck?
  YAML.quick_emit(nil, opts) do |out|
    string = to_s
    out.scalar(YAML_TAG, YAML_MAPPING[string] || string, :plain)
  end
end