std_json
std_json copied to clipboard
nlohmann
A proposal for a JSON data type in the C++ standard library
"...C++20 keyword char8_t brings (at last) the UTF-8 to the C++..." https://dbj.org/c-char8_t-is-broken/ There is a lot to read, but the first few paragraphs are enough.
I see there are these signatures mentioned in the [current proposal](https://github.com/nlohmann/std_json/blob/640d731195d35c438b0ddd507b4b181eaf531f89/proposal.md#object-element-access-by-key-with-default-value): ``` string_type value(const typename object_type::key_type &, const char * default_value) const; ``` ``` string_type value(const json_pointer &, const char...
To submit the proposal, it has to be in [HTML or PDF format](https://isocpp.org/std/standing-documents/sd-7-mailing-procedures-and-how-to-write-papers. For the latter, the [repository of the C++ standard draft](https://github.com/cplusplus/draft/tree/master/source) can be used to take [a lot...
The [README](https://github.com/nlohmann/json/blob/develop/README.md) and the GIF from nlohmann/json contain a lot of small examples to motivate having a JSON datatype inside C++. They also allow to exemplify the design goals (i.e.,...
In my opinion, there should be several pieces: 1. Json lexer ([gason](https://github.com/vivkin/gason) is excellent for this.) * One advantage is that the lexer could handle arbitrarily long ints and floats....
This may be still fine if we only accept stateless allocators. E.g. `std::allocator` is fine, but `std::pmr::polymorphic_allocator` is not. However, if so, we should require `allocator_traits::is_always_equal::value` to be `true` somewhere.
[[contents]/2](https://eel.is/c++draft/contents#2) already allows implementations to put the components into an inline namespace in `std`. So, it seems overspecified to require using an inline namepace of a specified name `json_v1`.