Niels Lohmann
6a852ab96d
* Split the json_view feature page into sub-pages
The single features/json_view.md page grew to ~600 lines covering eight
topics. Split it into features/json_view/ with an overview page and
pages for ownership and lifetime, differences from basic_json, reading
values, generic code, editing, and images.
The new differences page collects what was spread over several sections
("What is the same", "What is different", "Duplicate keys", and notes in
the conversion and serialization sections) under one summary table, and
adds the parts of the basic_json interface a view does not have. The
other pages now link to it instead of restating the rules.
Internal links across the documentation point to the new pages.
Signed-off-by: Niels Lohmann <mail@nlohmann.me>
* Docs: fix stale comments and trim repeated text in json_view pages
- fig-jsonview.js/.css: point the header comments at the new pages
- reading.md: views' strings are valid as long as the document (and a
borrowed source text), as lifetime.md says
- reading.md, generic_code.md: link to differences.md instead of
restating the member-order and repeated-key rules
- differences.md: drop the third mention of ordering comparisons, name
rbegin()/rend() in the iterator row
- exceptions.md: link editable documents to editing.md
Signed-off-by: Niels Lohmann <mail@nlohmann.me>
---------
Signed-off-by: Niels Lohmann <mail@nlohmann.me>
1.8 KiB
1.8 KiB
nlohmann::is_json_view
Defined in header <nlohmann/json_view.hpp>
template<typename T>
struct is_json_view;
A type trait: #!cpp is_json_view<T>::value is #!cpp true if T is a basic_json_view
of any BasicJsonType and any view_mode -- json_view,
json_editable_view, ordered_json_view, ... -- and
#!cpp false otherwise, for basic_json as well.
It is meant for constraining templates that accept views, in particular a from_json() that should read views
directly: get<T>() on a view calls a from_json() with the view only if that from_json()
accepts views but not arbitrary types.
Template parameters
T- the type to check (without cv-qualifiers or references)
Notes
A view is recognized by its member type basic_json_type (a basic_json specialization) and
its materialize() returning that type, so the trait needs no declaration of the
view class.
Examples
??? example
The example below shows the trait, and a `from_json()` constrained to `json` values and views: `get<T>()` on a view
reads the view directly.
```cpp
--8<-- "examples/is_json_view.cpp"
```
Output:
```
--8<-- "examples/is_json_view.output"
```
See also
- basic_json_view - a handle to one value of a document
- get - which conversions read the view directly
- view_mode - read-only or editable
- Writing generic code - functions and
from_json()for views
Version history
Added in version 3.13.0.