tobid7/renderd7
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Documentation1

Browse Source
This commit is contained in:
tobid7
2022-04-12 08:58:20 +00:00
parent 9341e4ff74
commit 311da5fc4c
18 changed files with 707 additions and 752 deletions
Download Patch File Download Diff File Expand all files Collapse all files

64
classnlohmann_1_1basic__json.html
View File

@ -1420,7 +1420,7 @@ JSON Merge Patch functions</h2></td></tr>
</table>
</dd>
</dl>
<h4><a class="anchor" id="autotoc_md6"></a>
<h4><a class="anchor" id="autotoc_md0"></a>
Default type</h4>
<p>With the default values for <em>ObjectType</em> (<code>std::map</code>), <em>StringType</em> (<code>std::string</code>), and <em>AllocatorType</em> (<code>std::allocator</code>), the default value for <em>object_t</em> is:</p>
<div class="fragment"><div class="line">std::map&lt;</div>
@ -1429,7 +1429,7 @@ Default type</h4>
<div class="line"> std::less&lt;std::string&gt;, <span class="comment">// key_compare</span></div>
<div class="line"> std::allocator&lt;std::pair&lt;const std::string, basic_json&gt;&gt; <span class="comment">// allocator_type</span></div>
<div class="line">&gt;</div>
</div><!-- fragment --><h4><a class="anchor" id="autotoc_md7"></a>
</div><!-- fragment --><h4><a class="anchor" id="autotoc_md1"></a>
Behavior</h4>
<p>The choice of <em>object_t</em> influences the behavior of the JSON class. With the default type, objects have the following behavior:</p>
<ul>
@ -1438,13 +1438,13 @@ Behavior</h4>
<li>Internally, name/value pairs are stored in lexicographical order of the names. Objects will also be serialized (see <a class="el" href="classnlohmann_1_1basic__json.html#acfc564f36da667b7d9109879d34dc36c">dump</a>) in this order. For instance, <code>{"b": 1, "a": 2}</code> and <code>{"a": 2, "b": 1}</code> will be stored and serialized as <code>{"a": 2, "b": 1}</code>.</li>
<li>When comparing objects, the order of the name/value pairs is irrelevant. This makes objects interoperable in the sense that they will not be affected by these differences. For instance, <code>{"b": 1, "a": 2}</code> and <code>{"a": 2, "b": 1}</code> will be treated as equal.</li>
</ul>
<h4><a class="anchor" id="autotoc_md8"></a>
<h4><a class="anchor" id="autotoc_md2"></a>
Limits</h4>
<p><a href="http://rfc7159.net/rfc7159">RFC 7159</a> specifies: </p><blockquote class="doxtable">
<p>An implementation may set limits on the maximum depth of nesting. </p>
</blockquote>
<p>In this class, the object's limit of nesting is not explicitly constrained. However, a maximum depth of nesting may be introduced by the compiler or runtime environment. A theoretical limit can be queried by calling the <a class="el" href="classnlohmann_1_1basic__json.html#a502e4020141ed42d55e5d1fd88b3e80f">max_size</a> function of a JSON object.</p>
<h4><a class="anchor" id="autotoc_md9"></a>
<h4><a class="anchor" id="autotoc_md3"></a>
Storage</h4>
<p>Objects are stored as pointers in a <a class="el" href="classnlohmann_1_1basic__json.html">basic_json</a> type. That is, for any access to object values, a pointer of type <code>object_t*</code> must be dereferenced.</p>
<dl class="section see"><dt>See also</dt><dd><a class="el" href="classnlohmann_1_1basic__json.html#a69524b1f8f42c0a81b86cee3fc54e034">array_t</a> &ndash; <a class="el" href="classnlohmann_1_1basic__json.html#a530ad60b7fb590e0ee45b6803144cc00" title="return the type of the JSON value (explicit)">type</a> for an <a class="el" href="classnlohmann_1_1basic__json.html#aea7fc2a66a785e2f68535f63b54150a9" title="explicitly create an array from an initializer list">array</a> <a class="el" href="classnlohmann_1_1basic__json.html#ab29a59d20767180d6d2fe4f5054dd245" title="access specified object element with default value">value</a></dd></dl>
@ -1477,20 +1477,20 @@ Storage</h4>
</table>
</dd>
</dl>
<h4><a class="anchor" id="autotoc_md10"></a>
<h4><a class="anchor" id="autotoc_md4"></a>
Default type</h4>
<p>With the default values for <em>ArrayType</em> (<code>std::vector</code>) and <em>AllocatorType</em> (<code>std::allocator</code>), the default value for <em>array_t</em> is:</p>
<div class="fragment"><div class="line">std::vector&lt;</div>
<div class="line"> <a class="code" href="classnlohmann_1_1basic__json.html#ad886f4baa2efb7ac6b0ca70dc72f3d18">basic_json</a>, <span class="comment">// value_type</span></div>
<div class="line"> std::allocator&lt;basic_json&gt; <span class="comment">// allocator_type</span></div>
<div class="line">&gt;</div>
</div><!-- fragment --><h4><a class="anchor" id="autotoc_md11"></a>
</div><!-- fragment --><h4><a class="anchor" id="autotoc_md5"></a>
Limits</h4>
<p><a href="http://rfc7159.net/rfc7159">RFC 7159</a> specifies: </p><blockquote class="doxtable">
<p>An implementation may set limits on the maximum depth of nesting. </p>
</blockquote>
<p>In this class, the array's limit of nesting is not explicitly constrained. However, a maximum depth of nesting may be introduced by the compiler or runtime environment. A theoretical limit can be queried by calling the <a class="el" href="classnlohmann_1_1basic__json.html#a502e4020141ed42d55e5d1fd88b3e80f">max_size</a> function of a JSON array.</p>
<h4><a class="anchor" id="autotoc_md12"></a>
<h4><a class="anchor" id="autotoc_md6"></a>
Storage</h4>
<p>Arrays are stored as pointers in a <a class="el" href="classnlohmann_1_1basic__json.html">basic_json</a> type. That is, for any access to array values, a pointer of type <code>array_t*</code> must be dereferenced.</p>
<dl class="section see"><dt>See also</dt><dd><a class="el" href="classnlohmann_1_1basic__json.html#a949272bf6af5eb8eab9675505422f5b3">object_t</a> &ndash; <a class="el" href="classnlohmann_1_1basic__json.html#a530ad60b7fb590e0ee45b6803144cc00" title="return the type of the JSON value (explicit)">type</a> for an <a class="el" href="classnlohmann_1_1basic__json.html#a10c8164cc94feabf095b959633c0d709" title="explicitly create an object from an initializer list">object</a> <a class="el" href="classnlohmann_1_1basic__json.html#ab29a59d20767180d6d2fe4f5054dd245" title="access specified object element with default value">value</a></dd></dl>
@ -1521,20 +1521,20 @@ Storage</h4>
</table>
</dd>
</dl>
<h4><a class="anchor" id="autotoc_md13"></a>
<h4><a class="anchor" id="autotoc_md7"></a>
Default type</h4>
<p>With the default values for <em>StringType</em> (<code>std::string</code>), the default value for <em>string_t</em> is:</p>
<div class="fragment"><div class="line">std::string</div>
</div><!-- fragment --><h4><a class="anchor" id="autotoc_md14"></a>
</div><!-- fragment --><h4><a class="anchor" id="autotoc_md8"></a>
Encoding</h4>
<p>Strings are stored in UTF-8 encoding. Therefore, functions like <code>std::string::size()</code> or <code>std::string::length()</code> return the number of bytes in the string rather than the number of characters or glyphs.</p>
<h4><a class="anchor" id="autotoc_md15"></a>
<h4><a class="anchor" id="autotoc_md9"></a>
String comparison</h4>
<p><a href="http://rfc7159.net/rfc7159">RFC 7159</a> states: </p><blockquote class="doxtable">
<p>Software implementations are typically required to test names of object members for equality. Implementations that transform the textual representation into sequences of Unicode code units and then perform the comparison numerically, code unit by code unit, are interoperable in the sense that implementations will agree in all cases on equality or inequality of two strings. For example, implementations that compare strings with escaped characters unconverted may incorrectly find that <code>"a\\b"</code> and <code>"a\u005Cb"</code> are not equal. </p>
</blockquote>
<p>This implementation is interoperable as it does compare strings code unit by code unit.</p>
<h4><a class="anchor" id="autotoc_md16"></a>
<h4><a class="anchor" id="autotoc_md10"></a>
Storage</h4>
<p>String values are stored as pointers in a <a class="el" href="classnlohmann_1_1basic__json.html">basic_json</a> type. That is, for any access to string values, a pointer of type <code>string_t*</code> must be dereferenced.</p>
<dl class="section since"><dt>Since</dt><dd>version 1.0.0 </dd></dl>
@ -1556,11 +1556,11 @@ Storage</h4>
<p>a type for a boolean </p>
<p><a href="http://rfc7159.net/rfc7159">RFC 7159</a> implicitly describes a boolean as a type which differentiates the two literals <code>true</code> and <code>false</code>.</p>
<p>To store objects in C++, a type is defined by the template parameter <em>BooleanType</em> which chooses the type to use.</p>
<h4><a class="anchor" id="autotoc_md17"></a>
<h4><a class="anchor" id="autotoc_md11"></a>
Default type</h4>
<p>With the default values for <em>BooleanType</em> (<code>bool</code>), the default value for <em>boolean_t</em> is:</p>
<div class="fragment"><div class="line"><span class="keywordtype">bool</span></div>
</div><!-- fragment --><h4><a class="anchor" id="autotoc_md18"></a>
</div><!-- fragment --><h4><a class="anchor" id="autotoc_md12"></a>
Storage</h4>
<p>Boolean values are stored directly inside a <a class="el" href="classnlohmann_1_1basic__json.html">basic_json</a> type.</p>
<dl class="section since"><dt>Since</dt><dd>version 1.0.0 </dd></dl>
@ -1585,17 +1585,17 @@ Storage</h4>
</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, <a class="el" href="classnlohmann_1_1basic__json.html#ab227d71ad47b6ed6a3acae52dedbb49d">number_integer_t</a>, <a class="el" href="classnlohmann_1_1basic__json.html#a440094de5ef4e119b2771b549b33da70">number_unsigned_t</a> and <a class="el" href="classnlohmann_1_1basic__json.html#ade1eb06e9fc3ff2ba1efd709b94b401d">number_float_t</a> are used.</p>
<p>To store integer numbers in C++, a type is defined by the template parameter <em>NumberIntegerType</em> which chooses the type to use.</p>
<h4><a class="anchor" id="autotoc_md19"></a>
<h4><a class="anchor" id="autotoc_md13"></a>
Default type</h4>
<p>With the default values for <em>NumberIntegerType</em> (<code>int64_t</code>), the default value for <em>number_integer_t</em> is:</p>
<div class="fragment"><div class="line">int64_t</div>
</div><!-- fragment --><h4><a class="anchor" id="autotoc_md20"></a>
</div><!-- fragment --><h4><a class="anchor" id="autotoc_md14"></a>
Default behavior</h4>
<ul>
<li>The restrictions about leading zeros is not enforced in C++. Instead, leading zeros in integer literals lead to an interpretation as octal number. Internally, the value will be stored as decimal number. For instance, the C++ integer literal <code>010</code> will be serialized to <code>8</code>. During deserialization, leading zeros yield an error.</li>
<li>Not-a-number (NaN) values will be serialized to <code>null</code>.</li>
</ul>
<h4><a class="anchor" id="autotoc_md21"></a>
<h4><a class="anchor" id="autotoc_md15"></a>
Limits</h4>
<p><a href="http://rfc7159.net/rfc7159">RFC 7159</a> specifies: </p><blockquote class="doxtable">
<p>An implementation may set limits on the range and precision of numbers. </p>
@ -1605,7 +1605,7 @@ Limits</h4>
<p>Note that when such software is used, numbers that are integers and are in the range <img class="formulaInl" alt="$[-2^{53}+1, 2^{53}-1]$" src="form_0.png"/> are interoperable in the sense that implementations will agree exactly on their numeric values. </p>
</blockquote>
<p>As this range is a subrange of the exactly supported range [INT64_MIN, INT64_MAX], this class's integer type is interoperable.</p>
<h4><a class="anchor" id="autotoc_md22"></a>
<h4><a class="anchor" id="autotoc_md16"></a>
Storage</h4>
<p>Integer number values are stored directly inside a <a class="el" href="classnlohmann_1_1basic__json.html">basic_json</a> type.</p>
<dl class="section see"><dt>See also</dt><dd><a class="el" href="classnlohmann_1_1basic__json.html#ade1eb06e9fc3ff2ba1efd709b94b401d">number_float_t</a> &ndash; <a class="el" href="classnlohmann_1_1basic__json.html#a530ad60b7fb590e0ee45b6803144cc00" title="return the type of the JSON value (explicit)">type</a> for number values (floating-point)</dd>
@ -1633,17 +1633,17 @@ Storage</h4>
</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, <a class="el" href="classnlohmann_1_1basic__json.html#ab227d71ad47b6ed6a3acae52dedbb49d">number_integer_t</a>, <a class="el" href="classnlohmann_1_1basic__json.html#a440094de5ef4e119b2771b549b33da70">number_unsigned_t</a> and <a class="el" href="classnlohmann_1_1basic__json.html#ade1eb06e9fc3ff2ba1efd709b94b401d">number_float_t</a> are used.</p>
<p>To store unsigned integer numbers in C++, a type is defined by the template parameter <em>NumberUnsignedType</em> which chooses the type to use.</p>
<h4><a class="anchor" id="autotoc_md23"></a>
<h4><a class="anchor" id="autotoc_md17"></a>
Default type</h4>
<p>With the default values for <em>NumberUnsignedType</em> (<code>uint64_t</code>), the default value for <em>number_unsigned_t</em> is:</p>
<div class="fragment"><div class="line">uint64_t</div>
</div><!-- fragment --><h4><a class="anchor" id="autotoc_md24"></a>
</div><!-- fragment --><h4><a class="anchor" id="autotoc_md18"></a>
Default behavior</h4>
<ul>
<li>The restrictions about leading zeros is not enforced in C++. Instead, leading zeros in integer literals lead to an interpretation as octal number. Internally, the value will be stored as decimal number. For instance, the C++ integer literal <code>010</code> will be serialized to <code>8</code>. During deserialization, leading zeros yield an error.</li>
<li>Not-a-number (NaN) values will be serialized to <code>null</code>.</li>
</ul>
<h4><a class="anchor" id="autotoc_md25"></a>
<h4><a class="anchor" id="autotoc_md19"></a>
Limits</h4>
<p><a href="http://rfc7159.net/rfc7159">RFC 7159</a> specifies: </p><blockquote class="doxtable">
<p>An implementation may set limits on the range and precision of numbers. </p>
@ -1653,7 +1653,7 @@ Limits</h4>
<p>Note that when such software is used, numbers that are integers and are in the range <img class="formulaInl" alt="$[-2^{53}+1, 2^{53}-1]$" src="form_0.png"/> are interoperable in the sense that implementations will agree exactly on their numeric values. </p>
</blockquote>
<p>As this range is a subrange (when considered in conjunction with the number_integer_t type) of the exactly supported range [0, UINT64_MAX], this class's integer type is interoperable.</p>
<h4><a class="anchor" id="autotoc_md26"></a>
<h4><a class="anchor" id="autotoc_md20"></a>
Storage</h4>
<p>Integer number values are stored directly inside a <a class="el" href="classnlohmann_1_1basic__json.html">basic_json</a> type.</p>
<dl class="section see"><dt>See also</dt><dd><a class="el" href="classnlohmann_1_1basic__json.html#ade1eb06e9fc3ff2ba1efd709b94b401d">number_float_t</a> &ndash; <a class="el" href="classnlohmann_1_1basic__json.html#a530ad60b7fb590e0ee45b6803144cc00" title="return the type of the JSON value (explicit)">type</a> for number values (floating-point) </dd>
@ -1681,23 +1681,23 @@ Storage</h4>
</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, <a class="el" href="classnlohmann_1_1basic__json.html#ab227d71ad47b6ed6a3acae52dedbb49d">number_integer_t</a>, <a class="el" href="classnlohmann_1_1basic__json.html#a440094de5ef4e119b2771b549b33da70">number_unsigned_t</a> and <a class="el" href="classnlohmann_1_1basic__json.html#ade1eb06e9fc3ff2ba1efd709b94b401d">number_float_t</a> are used.</p>
<p>To store floating-point numbers in C++, a type is defined by the template parameter <em>NumberFloatType</em> which chooses the type to use.</p>
<h4><a class="anchor" id="autotoc_md27"></a>
<h4><a class="anchor" id="autotoc_md21"></a>
Default type</h4>
<p>With the default values for <em>NumberFloatType</em> (<code>double</code>), the default value for <em>number_float_t</em> is:</p>
<div class="fragment"><div class="line"><span class="keywordtype">double</span></div>
</div><!-- fragment --><h4><a class="anchor" id="autotoc_md28"></a>
</div><!-- fragment --><h4><a class="anchor" id="autotoc_md22"></a>
Default behavior</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>
<h4><a class="anchor" id="autotoc_md29"></a>
<h4><a class="anchor" id="autotoc_md23"></a>
Limits</h4>
<p><a href="http://rfc7159.net/rfc7159">RFC 7159</a> states: </p><blockquote class="doxtable">
<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>
<h4><a class="anchor" id="autotoc_md30"></a>
<h4><a class="anchor" id="autotoc_md24"></a>
Storage</h4>
<p>Floating-point number values are stored directly inside a <a class="el" href="classnlohmann_1_1basic__json.html">basic_json</a> type.</p>
<dl class="section see"><dt>See also</dt><dd><a class="el" href="classnlohmann_1_1basic__json.html#ab227d71ad47b6ed6a3acae52dedbb49d">number_integer_t</a> &ndash; <a class="el" href="classnlohmann_1_1basic__json.html#a530ad60b7fb590e0ee45b6803144cc00" title="return the type of the JSON value (explicit)">type</a> for number values (integer)</dd>
@ -1733,13 +1733,13 @@ Storage</h4>
</blockquote>
<p>None of these impose any limitations on the internal representation other than the basic unit of storage be some type of array whose parts are decomposable into bytes.</p>
<p>The default representation of this binary format is a <code>std::vector&lt;std::uint8_t&gt;</code>, which is a very common way to represent a byte array in modern C++.</p>
<h4><a class="anchor" id="autotoc_md31"></a>
<h4><a class="anchor" id="autotoc_md25"></a>
Default type</h4>
<p>The default values for <em>BinaryType</em> is <code>std::vector&lt;std::uint8_t&gt;</code></p>
<h4><a class="anchor" id="autotoc_md32"></a>
<h4><a class="anchor" id="autotoc_md26"></a>
Storage</h4>
<p>Binary Arrays are stored as pointers in a <a class="el" href="classnlohmann_1_1basic__json.html">basic_json</a> type. That is, for any access to array values, a pointer of the type <code>binary_t*</code> must be dereferenced.</p>
<h4><a class="anchor" id="autotoc_md33"></a>
<h4><a class="anchor" id="autotoc_md27"></a>
Notes on subtypes</h4>
<ul>
<li>CBOR<ul>
@ -6056,7 +6056,7 @@ Illustration from cppreference.com</div></div>
<p>@exceptionsafety Strong guarantee: if an exception is thrown, there are no changes in the JSON value.</p>
<p>@complexity Constant.</p>
<dl class="section note"><dt>Note</dt><dd>The name of this function is not yet final and may change in the future.</dd></dl>
<dl class="deprecated"><dt><b><a class="el" href="deprecated.html#_deprecated000002">Deprecated:</a></b></dt><dd>This stream operator is deprecated and will be removed in future 4.0.0 of the library. Please use <a class="el" href="classnlohmann_1_1basic__json.html#a5961446010dfc494e0c247b4e9026977">items()</a> instead; that is, replace <code>json::iterator_wrapper(j)</code> with <code>j.items()</code>. </dd></dl>
<dl class="deprecated"><dt><b><a class="el" href="deprecated.html#_deprecated000001">Deprecated:</a></b></dt><dd>This stream operator is deprecated and will be removed in future 4.0.0 of the library. Please use <a class="el" href="classnlohmann_1_1basic__json.html#a5961446010dfc494e0c247b4e9026977">items()</a> instead; that is, replace <code>json::iterator_wrapper(j)</code> with <code>j.items()</code>. </dd></dl>
</div>
</div>
@ -6114,7 +6114,7 @@ Illustration from cppreference.com</div></div>
<p>@exceptionsafety Strong guarantee: if an exception is thrown, there are no changes in the JSON value.</p>
<p>@complexity Constant.</p>
<dl class="section note"><dt>Note</dt><dd>The name of this function is not yet final and may change in the future.</dd></dl>
<dl class="deprecated"><dt><b><a class="el" href="deprecated.html#_deprecated000002">Deprecated:</a></b></dt><dd>This stream operator is deprecated and will be removed in future 4.0.0 of the library. Please use <a class="el" href="classnlohmann_1_1basic__json.html#a5961446010dfc494e0c247b4e9026977">items()</a> instead; that is, replace <code>json::iterator_wrapper(j)</code> with <code>j.items()</code>. </dd></dl>
<dl class="deprecated"><dt><b><a class="el" href="deprecated.html#_deprecated000001">Deprecated:</a></b></dt><dd>This stream operator is deprecated and will be removed in future 4.0.0 of the library. Please use <a class="el" href="classnlohmann_1_1basic__json.html#a5961446010dfc494e0c247b4e9026977">items()</a> instead; that is, replace <code>json::iterator_wrapper(j)</code> with <code>j.items()</code>. </dd></dl>
</div>
</div>
@ -11049,7 +11049,7 @@ template&lt;typename ScalarType , typename std::enable_if&lt; std::is_scalar&lt;
</div><div class="memdoc">
<p>serialize to stream </p>
<dl class="deprecated"><dt><b><a class="el" href="deprecated.html#_deprecated000003">Deprecated:</a></b></dt><dd>This stream operator is deprecated and will be removed in future 4.0.0 of the library. Please use <a class="el" href="classnlohmann_1_1basic__json.html#a5e34c5435e557d0bf666bd7311211405">operator&lt;&lt;(std::ostream&amp;, const basic_json&amp;)</a> instead; that is, replace calls like <code>j &gt;&gt; o;</code> with <code>o &lt;&lt; j;</code>. </dd></dl>
<dl class="deprecated"><dt><b><a class="el" href="deprecated.html#_deprecated000002">Deprecated:</a></b></dt><dd>This stream operator is deprecated and will be removed in future 4.0.0 of the library. Please use <a class="el" href="classnlohmann_1_1basic__json.html#a5e34c5435e557d0bf666bd7311211405">operator&lt;&lt;(std::ostream&amp;, const basic_json&amp;)</a> instead; that is, replace calls like <code>j &gt;&gt; o;</code> with <code>o &lt;&lt; j;</code>. </dd></dl>
<dl class="section since"><dt>Since</dt><dd>version 1.0.0; deprecated since version 3.0.0 </dd></dl>
</div>
@ -11089,7 +11089,7 @@ template&lt;typename ScalarType , typename std::enable_if&lt; std::is_scalar&lt;
</div><div class="memdoc">
<p>deserialize from stream </p>
<dl class="deprecated"><dt><b><a class="el" href="deprecated.html#_deprecated000004">Deprecated:</a></b></dt><dd>This stream operator is deprecated and will be removed in version 4.0.0 of the library. Please use <a class="el" href="classnlohmann_1_1basic__json.html#aaf363408931d76472ded14017e59c9e8">operator&gt;&gt;(std::istream&amp;, basic_json&amp;)</a> instead; that is, replace calls like <code>j &lt;&lt; i;</code> with <code>i &gt;&gt; j;</code>. </dd></dl>
<dl class="deprecated"><dt><b><a class="el" href="deprecated.html#_deprecated000003">Deprecated:</a></b></dt><dd>This stream operator is deprecated and will be removed in version 4.0.0 of the library. Please use <a class="el" href="classnlohmann_1_1basic__json.html#aaf363408931d76472ded14017e59c9e8">operator&gt;&gt;(std::istream&amp;, basic_json&amp;)</a> instead; that is, replace calls like <code>j &lt;&lt; i;</code> with <code>i &gt;&gt; j;</code>. </dd></dl>
<dl class="section since"><dt>Since</dt><dd>version 1.0.0; deprecated since version 3.0.0 </dd></dl>
</div>