</code></pre></div><p>The type used to store JSON numbers (floating-point).</p><p><ahref=https://tools.ietf.org/html/rfc8259>RFC 8259</a> describes numbers as follows:</p><blockquote><p>The representation of numbers is similar to that used in most programming languages. A number is represented in base 10 using decimal digits. It contains an integer component that may be prefixed with an optional minus sign, which may be followed by a fraction part and/or an exponent part. Leading zeros are not allowed. (...) Numeric values that cannot be represented in the grammar below (such as Infinity and NaN) are not permitted.</p></blockquote><p>This description includes both integer and floating-point numbers. However, C++ allows more precise storage if it is known whether the number is a signed integer, an unsigned integer or a floating-point number. Therefore, three different types, <ahref=../number_integer_t/><code>number_integer_t</code></a>, <ahref=../number_unsigned_t/><code>number_unsigned_t</code></a> and <code>number_float_t</code> are used.</p><p>To store floating-point numbers in C++, a type is defined by the template parameter <code>NumberFloatType</code> which chooses the type to use.</p><h2id=notes>Notes<aclass=headerlinkhref=#notestitle="Permanent link">¶</a></h2><h4id=default-type>Default type<aclass=headerlinkhref=#default-typetitle="Permanent link">¶</a></h4><p>With the default values for <code>NumberFloatType</code> (<code>double</code>), the default value for <code>number_float_t</code> is <codeclass=highlight><spanclass=kt>double</span></code>.</p><h4id=default-behavior>Default behavior<aclass=headerlinkhref=#default-behaviortitle="Permanent link">¶</a></h4><ul><li>The restrictions about leading zeros is not enforced in C++. Instead, leading zeros in floating-point literals will be ignored. Internally, the value will be stored as decimal number. For instance, the C++ floating-point literal <code>01.2</code> will be serialized to <code>1.2</code>. During deserialization, leading zeros yield an error.</li><li>Not-a-number (NaN) values will be serialized to <code>null</code>.</li></ul><h4id=limits>Limits<aclass=headerlinkhref=#limitstitle="Permanent link">¶</a></h4><p><ahref=https://tools.ietf.org/html/rfc8259>RFC 8259</a> states:</p><blockquote><p>This specification allows implementations to set limits on the range and precision of numbers accepted. Since software that implements IEEE 754-2008 binary64 (double precision) numbers is generally available and widely used, good interoperability can be achieved by implementations that expect no more precision or range than these provide, in the sense that implementations will approximate JSON numbers within the expected precision.</p></blockquote><p>This implementation does exactly follow this approach, as it uses double precision floating-point numbers. Note values smaller than <code>-1.79769313486232e+308</code> and values greater than <code>1.79769313486232e+308</code> will be stored as NaN internally and be serialized to <code>null</code>.</p><h4id=storage>Storage<aclass=headerlinkhref=#storagetitle="Permanent link">¶</a></h4><p>Floating-point number values are stored directly inside a <code>basic_json</code> type.</p><h2id=examples>Examples<aclass=headerlinkhref=#examplestitle="Permanent link">¶</a></h2><detailsclass=example><summary>Example</summary><p>The following code shows that <code>number_float_t</code> is by default, a typedef to <codeclass=highlight><spanclass=kt>double</span></code>.</p><divclass=highlight><pre><span></span><code><spanclass=cp>#include</span><spanclass=w></span><spanclass=cpf><iostream></span>
