* docs: new design for the documentation site Apply the brand to the Material for MkDocs site: Inter and JetBrains Mono served by the site (upright and real italic), brand colours, blue header band with the syntax pattern, wordmark in the header, new home page (hero, cards, animated feature tour), 404 page, polish for tabs, search, footer, focus rings, tables and code blocks, and theme features (code copy, previous/next footer, TOC follow, search suggestions). Draw the number railroad diagram, the parser callback events and the iterator illustrations as inline SVGs that follow the light and dark scheme. The generator scripts are in docs/mkdocs/scripts/figures; the feature slideshow (json-light.svg, json-dark.svg, replacing json.gif on the home page) is built by docs/mkdocs/scripts/slideshow. Decision nodes in five flowcharts become hexagons, which need far less room. Signed-off-by: Niels Lohmann <mail@nlohmann.me> * docs: add figures, table captions and a macro chooser - Figures with numbered captions: SAX stepper, json_view layout and edit stepper, exception map, JSON pointer and patch walkers, QA pipeline, scaling and binary size charts, roadmap lanes, release timeline, integration decision tree and namespace builder - Table captions (nj-table-caption) on 9 pages - Compile times: modules and PCH charts, filesystem section, re-measured Figure 1, links between features/modules.md and compile_times.md - Interactive macro chooser for features/arbitrary_types.md - Link check: exclude URLs that answer the plugin with 400/401/419 or are dead (customers.md) Signed-off-by: Niels Lohmann <mail@nlohmann.me> * docs: macro chooser generates adl_serializer for non-default-constructible types Signed-off-by: Niels Lohmann <mail@nlohmann.me> * docs: cross-link concept pages and API pages in See also sections Add See also links in both directions between the concept pages (features, home, integration) and the API pages, write API links in code font, give every entry a comment after a dash, and show the callback event figure on the parser callbacks page. Signed-off-by: Niels Lohmann <mail@nlohmann.me> * docs: address review comments on the new design - Home: add a "Latest release" button - Sponsors: update the list and group it by tier - Features: list all feature pages on the index page - Releases: add highlights per release, link the 4.0 roadmap, add the first commit to the timeline - Exceptions: prefix all example messages with the exception name - API: no code font for format names in the See also links of the to_/from_ pages - Merge Patch: show the document before, the patch, and the result - Replace "--" with typographic dashes, mark external links with an icon, center Mermaid diagrams Signed-off-by: Niels Lohmann <mail@nlohmann.me> --------- Signed-off-by: Niels Lohmann <mail@nlohmann.me>
143 lines
6.1 KiB
Markdown
143 lines
6.1 KiB
Markdown
# <small>nlohmann::</small>operator>>(basic_json)
|
|
|
|
```cpp
|
|
std::istream& operator>>(std::istream& i, basic_json& j);
|
|
```
|
|
|
|
Deserializes an input stream to a JSON value.
|
|
|
|
## Parameters
|
|
|
|
`i` (in, out)
|
|
: input stream to read a serialized JSON value from
|
|
|
|
`j` (in, out)
|
|
: JSON value to write the deserialized input to
|
|
|
|
## Return value
|
|
|
|
the stream `i`
|
|
|
|
## Exception safety
|
|
|
|
Strong guarantee: if an exception is thrown, there are no changes in `j`.
|
|
|
|
## Exceptions
|
|
|
|
- Throws [`parse_error.101`](../home/exceptions.md#jsonexceptionparse_error101) in case of an unexpected token, or if
|
|
`i` has no stream buffer (`#!cpp i.rdbuf() == nullptr`, for instance `#!cpp std::istream(nullptr)`).
|
|
- If reading from `i` reaches the end of the input and `eofbit` is part of `i`'s
|
|
[`exceptions()`](https://en.cppreference.com/w/cpp/io/basic_ios/exceptions) mask, the `std::ios_base::failure`
|
|
thrown by `i` itself propagates instead of a `parse_error`, the same as it would for the standard library's own
|
|
extraction operators.
|
|
|
|
## Complexity
|
|
|
|
Linear in the length of the input. The parser is a predictive LL(1) parser.
|
|
|
|
## Notes
|
|
|
|
A UTF-8 byte order mark is silently ignored.
|
|
|
|
Invalid Unicode escapes and unpaired surrogates in the input are reported as
|
|
[`parse_error.101`](../home/exceptions.md#jsonexceptionparse_error101) with a detailed message.
|
|
|
|
`operator>>` parses exactly one JSON value, so it can be called repeatedly to read a sequence of concatenated JSON
|
|
values from the same stream:
|
|
|
|
```cpp
|
|
json j1, j2;
|
|
input >> j1; // parses the first value
|
|
input >> j2; // parses the next value
|
|
```
|
|
|
|
!!! warning "A number must be followed by whitespace"
|
|
|
|
A number is only terminated by the character that follows it. That character is read from the stream to detect the
|
|
end of the number, and it is **not** put back. When a value that is a number is immediately followed by the next
|
|
value, the first character of that next value is lost:
|
|
|
|
```cpp
|
|
std::istringstream input("1true");
|
|
json j1, j2;
|
|
input >> j1; // j1 == 1
|
|
input >> j2; // throws parse_error.101: the stream now starts at "rue"
|
|
```
|
|
|
|
Separating the values with whitespace avoids this, because the character that is eaten is then the separator:
|
|
|
|
```cpp
|
|
std::istringstream input("1 true");
|
|
json j1, j2;
|
|
input >> j1; // j1 == 1
|
|
input >> j2; // j2 == true
|
|
```
|
|
|
|
Only numbers are affected. Values ending in a self-delimiting character do not read past themselves, so
|
|
`truefalse`, `[1][2]`, `{"a":1}{"b":2}`, and `"a""b"` can be read back to back without a separator.
|
|
|
|
Define [`JSON_PRECISE_STREAM_POSITION`](macros/json_precise_stream_position.md) to `1` to leave the terminating character in the stream
|
|
instead, so that the stream is positioned right after the value for every value type and no separator is
|
|
needed. This is tracked in [#5340](https://github.com/nlohmann/json/issues/5340).
|
|
|
|
Note that reading concatenated values does **not** work for [JSON Lines](../features/parsing/json_lines.md)
|
|
(newline-delimited JSON) input — see that page for why and for the recommended alternative.
|
|
|
|
By default, a `'\0'` (NUL) byte encountered while reading a value is treated as end of input, rather than as an
|
|
ordinary (and, outside of a string, invalid) byte; see the [FAQ entry](../home/faq.md#nul-bytes-in-the-input) for
|
|
details and the [`JSON_STRICT_NUL_HANDLING`](macros/json_strict_nul_handling.md) macro to opt into rejecting it
|
|
instead. Because `operator>>` only parses a single value and does not require the rest of the stream to be consumed,
|
|
a NUL byte *after* a complete value has no effect on `operator>>` either way; it only matters while a value is still
|
|
being read.
|
|
|
|
!!! warning "Deprecation"
|
|
|
|
This function replaces function `#!cpp std::istream& operator<<(basic_json& j, std::istream& i)` which has
|
|
been deprecated in version 3.0.0. It will be removed in version 4.0.0. Please replace calls like `#!cpp j << i;`
|
|
with `#!cpp i >> j;`.
|
|
|
|
See the [migration guide](../integration/migration_guide.md#parsing) for how to update existing code.
|
|
|
|
## Examples
|
|
|
|
??? example
|
|
|
|
The example below shows how a JSON value is constructed by reading a serialization from a stream.
|
|
|
|
```cpp
|
|
--8<-- "examples/operator_deserialize.cpp"
|
|
```
|
|
|
|
Output:
|
|
|
|
```json
|
|
--8<-- "examples/operator_deserialize.output"
|
|
```
|
|
|
|
## See also
|
|
|
|
- [`accept`](basic_json/accept.md) - check if the input is valid JSON
|
|
- [`parse`](basic_json/parse.md) - deserialize from a compatible input
|
|
- [`JSON_STRICT_NUL_HANDLING`](macros/json_strict_nul_handling.md) - opt in to rejecting a NUL byte in the input
|
|
instead of treating it as end of input
|
|
- [`JSON_PRECISE_STREAM_POSITION`](macros/json_precise_stream_position.md) - opt in to leaving the stream positioned right after a number
|
|
- [`JSON_DISABLE_STREAM_BULK_SCAN`](macros/json_disable_stream_bulk_scan.md) - read the stream one character at a time
|
|
- [Parsing](../features/parsing/index.md) - overview of the parsing functions
|
|
- [JSON Lines](../features/parsing/json_lines.md) - newline-delimited JSON
|
|
- [Large, Streamed, and Partial Input](../features/parsing/large_and_partial_input.md) - chunked, concatenated, and very large input
|
|
|
|
## Version history
|
|
|
|
- Added in version 1.0.0.
|
|
- `JSON_STRICT_NUL_HANDLING` added in version 3.13.0 to optionally reject a NUL byte in the input instead of treating
|
|
it as end of input; planned to become the default in version 4.0.0.
|
|
- `JSON_PRECISE_STREAM_POSITION` added in version 3.13.0 to optionally leave the character that terminates a number in
|
|
the stream; planned to become the default in version 4.0.0.
|
|
- Fixed a null pointer dereference for an `std::istream` without a stream buffer (now throws `parse_error.101`), and a
|
|
crash (`std::terminate`) when `i` has `eofbit` in its exception mask, in version 3.13.0.
|
|
- Changed to the strong exception safety guarantee in version 3.13.0: `j` is no longer left with a partially parsed
|
|
value if parsing throws.
|
|
- Scans the characters in the stream buffer of `i` in bulk in version 3.13.0; the position of `i` after the call is
|
|
unchanged ([`JSON_DISABLE_STREAM_BULK_SCAN`](macros/json_disable_stream_bulk_scan.md) restores reading one character
|
|
at a time).
|