Investigate moving code from jsoncons fork to dragonfly

[abhijat]

We have an algorithm which is very useful to walk a json obj and perform actions on it in the jsoncons fork.

It might be useful to switch it into dragonfly and reduce the surface area of our fork.

[dranikpg]

I don't relly support pulling all kinds of dependencies directly into df and exploding it in size. What problem is not solvable with a custom fork? There are lots of options to abstract away any details

[romange]

I think you misunderstood the issue which is indeed written not very clearly. We have this change:
danielaparker/jsoncons@72f6c09

which is a part of our fork but maybe we can implement the same without doing intrusive changes in jsoncons.

[abhijat]

The idea is to use their public API that jsoncons now supports, and remove one patch that we added to our fork, so it might make keeping our code in sync with upstream easier because of lesser customizations.

Basically move jsoncons::basic_json::compute_memory_size to our repo, by implementing it using their public API (if possible), and drop that commit from our fork.