What's next for jsoncons

[danielaparker]

Currently working on:

• Revisit using std::from_chars for string to double if supported, while addressing std::from_chars parsing fails tests on Windows.

• Add loosess_bignum option. If true, reads out-of-range floating point numbers as strings with tag semantic_tag::bigdec, otherwise (current behavior) as negative or positive infinity. Defaults to true.

Planned 1.x enhancements:

• A jsoncons/views namespace including a read-only json_view on a json_container type that allows for high performance parsing.

• Extend support throughout the library for stateful allocators.

Things we're currently thinking about, and experimenting with:

• Define a few macros in the source to allow users to disable features they don’t need, such as reading or writing, json_type_traits support, UTF-8 validation, or checking for duplicates, to slim down the library footprint. Or to enable features such as fast floating-pointer conversion.

• Define the requirements that are needed for a type to satisfy each jsoncons extension's expectation for its Json template parameter. This will open up the way to allowing types other than basic_json.

On the horizon:

• A specialized pull parser to more efficiently support json_cursor (currently all cursers repurpose our push parsers, pausing after each event received).

• More uniform library support for non-string keys