We’re planning on a
2.0.0 release as we’ve already started breaking the API by removing the dependency on
Before going any further I wish to emphasize that nothing is set in stone yet and that’s mostly why I’m starting this thread. The github search does provide some partial answers for some of the questions we have but I want to hear the community thoughts before making any decisions. Hopefully this will help planning things out for a better
First we’d like to reduce the complexity of the
yojson's codebase and before considering so we’d be really interested in knowing which of
Yojson.Raw do you use and why?
We’d also like to know if anyone uses the custom
Variant constructions at all.
As you can imagine the idea is to get rid of those variants and have a single Yojson module with a single type
t which would hopefully satisfy everyone. That would make it easier to remove the dependency on
cppo and would make working on
yojson a better and more accessible experience.
Another point of interest is the
Util submodule. We’re wondering how widely used it is as we might consider improving its API a little bit.
Finally we’re curious how many people would be interested in
yojson-async packages with non-blocking io.
@mjambon I’d also love to hear your take on this!
Suggestions are obviously welcome as well!