kelbon

what interface it will provide?

So it will work with boost pfr/ boost describe struct or what? I need more low lower level interface with serializing strings/ints/keys etc

Such interface witih returning string will not match with output iterators, (for not copying string after it created), also i think such overload serialize(auto& value, options) may break many overloads...

i dont think it what i expect from direct serializing, i was about sax interface for writing string/integer/double etc similar to direct parsing interface

> Direct parsing doesn't provide a SAX interface in this library. It's the other way around: direct parsing is implemented on top of a SAX interface. > > That being...

> But this is exactly what direct serialisation achieves. See these: https://www.boost.org/doc/libs/1_87_0/libs/json/doc/html/json/ref/boost__json__serializer/reset/overload5.html https://www.boost.org/doc/libs/1_87_0/libs/json/doc/html/json/ref/boost__json__serialize/overload5.html how i can use it for my type?

> There appears to be some miscommunication. My first inclination was to answer with "by calling one of these functions with an object of your type". But that should be...

Now i using rapidjson for this functionality: https://rapidjson.org/classrapidjson_1_1_writer.html Its usefull, convenient and expandable, also seems to be easy to implement (more easy then json parsing etc)

> I don't think it would be possible to retrofit such interface to our serializer. The issue is that it would require complete reversal of its workflow. Moreover, such push-based...

Its interesting, can you provide minimal example with different behavior for WASM / other targets?