Before submitting an issue, please ensure that you have read the documentation:

• Basics is an overview of how to use simdjson and its APIs: https://github.com/simdjson/simdjson/blob/master/doc/basics.md
• Performance shows some more advanced scenarios and how to tune for them: https://github.com/simdjson/simdjson/blob/master/doc/performance.md
• Contributing: https://github.com/simdjson/simdjson/blob/master/CONTRIBUTING.md
• We follow the JSON specification as described by RFC 8259 (T. Bray, 2017).

We do not make changes to simdjson without clearly identifiable benefits, which typically means either performance improvements, bug fixes or new features. Avoid bike-shedding: we all have opinions about how to write code, but we want to focus on what makes simdjson objectively better.

Is your feature request related to a problem? Please describe.

I'd like to use this for the PostgreSQL infrastructure, which is in C, and, pertinently, has longjmp in it, making C++ exceptions a non-starter for that project. There are likely other projects in a similar situation.

Describe the solution you'd like

Ideally, something that could compile the current code to C, as the current single-header code does for C++.

I have some time to work on this, and the first part of that work would be learning the code base well enough to get some idea of what's involved with such a compilation.

Describe alternatives you've considered

• Forget about it.
• Port useful bits one at a time.
• Whine.

I'm most tempted by the second. The third is a non-starter.

Additional context

I'd love to know what a screenshot might look like for this project. Graphs, maybe?

Are you willing to contribute code or documentation toward this new feature?
If you plan to contribute to simdjson, please read our

• CONTRIBUTING guide: https://github.com/simdjson/simdjson/blob/master/CONTRIBUTING.md and our
• HACKING guide: https://github.com/simdjson/simdjson/blob/master/HACKING.md

Yep. Reading those now.