What's next for jsoncons

[danielaparker]

Currently working on:

• Support JMESPath Lexical Scoping using the new let expression, noting that JEP 18 has been approved.

• Fully support stateful allocators in the jsonschema extension.

Planned 1.x enhancements:

• 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. In particular, we're considering introducing a read-only json_view type that allows for high performance parsing and that can be used with, for example, the jsonschema extension.

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