Methods
- #
- A
- D
- E
- T
Constants
YAML_TAG | = | 'tag:yaml.org,2002:float' |
YAML_MAPPING | = | { 'Infinity' => '.Inf', '-Infinity' => '-.Inf', 'NaN' => '.NaN' } |
DEFAULT_STRING_FORMAT | = | 'F' |
Instance Public methods
_original_to_s(format = DEFAULT_STRING_FORMAT)
Link
as_json(options = nil)
Link
A BigDecimal would be naturally represented as a JSON number. Most libraries, however, parse non-integer JSON numbers directly as floats. Clients using those libraries would get in general a wrong number and no way to recover other than manually inspecting the string with the JSON code itself.
That’s why a JSON string is returned. The JSON literal is not numeric, but if the other end knows by contract that the data is supposed to be a BigDecimal, it still has the chance to post-process the string and get the real value.
duplicable?()
Link
encode_with(coder)
Link
to_d()
Link
to_yaml(opts = {})
Link
This emits the number without any scientific notation. This is better than self.to_f.to_s since it doesn’t lose precision.
Note that reconstituting YAML floats to native floats may lose precision.
# File activesupport/lib/active_support/core_ext/big_decimal/conversions.rb, line 18 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