Magic Enum C++ VS daw_json_link

I'm not sure this is quite what you're asking for, but this library has been super helpful to me in the past : https://github.com/Neargye/magic_enum

Also, a shoutout to Magic Enum: https://github.com/Neargye/magic_enum

What does this have to offer over magic_enum?

But it's a hack, and I prefer not to use hacks in production, because of their significant limitations:

You can either write a to string(view) function for your enum or use https://github.com/Neargye/magic_enum

Why reinvent the wheel? magic_enum

Also if you want to convert enum members to string representation I suggest you just use magic_enum instead, much smaller dependency.

Magic Enum provides that.

They might have good luck with https://github.com/beached/daw_json_link it has support for stuff like JSON lines and alike plus other ways that only use as much ram as their underlying data structures do as it parses directly to the user DS. Plus it has an iterator/range interface for things like arrays if needed.

We will add more benchmarks in the future, but for now you can see the comparison of daw_json_link with rapidjson. glaze is faster than daw_json_link, which is over twice as fast as rapidjson.

I am biased, but prefer https://github.com/beached/daw_json_link Super fast and you work with your native data structures without the overhead of DOM parsing/lookup

You can also look into https://github.com/beached/daw_json_link which claims to support nullable values in the readme.

The library I author does this. https://github.com/beached/daw_json_link . It's fast, GB/s too, and provides the mapping mechanism, iteration types, json lines support, event based parser, along with a non-owning json_value for when the mappings don't fit right or if one is querying. Pretty much everything but an owning JSON value as it's not something I've ever needed more than temporarily and brings a lot of complexity that is solved by using the actual C++ data structures one is eventually parsing into anyways.

So DAW JSON Link does have a DOM view, however it does not have a owning view. The json_value(even supports JSON Path in a limited form) type and json_raw mappings can help here. But there is no hard line between parsing view the json_value and the mappings to concrete data structures. One can mix and match.

Is this the repo? Never saw it linked in our convo, and I’d like to give it a whirl.

daw_json_link is what you're looking for : https://github.com/beached/daw_json_link

Check out https://github.com/beached/daw_json_link , it provides a non-typeerased way to parse JSON straight into user-defined data structures.