24 Nov
2019
24 Nov
'19
4:08 p.m.
On Sun, Nov 24, 2019 at 3:53 AM Bjorn Reese wrote:
If your design becomes a Boost library, then there will be very little incentive to include yet another JSON library to handle the remaining use case
As someone who is interested in a JSON library that handles some of those other use cases, I hope nobody feels that this is the case. i.e. There would be room for another library in Boost. If this library is accepted as "Boost.Json", that library could even be "Boost.Json2". Glen